Provide environment reproducibility

mataha commented 10 months ago

Description

This commit introduces environment reproducibility to the project. This is done by compiling a requirements file (via pip-compile) with all dependencies locked to specific versions (like lockfiles used by e.g. Node package managers) to achieve package consistency.

Motivation and Context

Locking down 2nd+ degree dependencies (especially pillow) to prevent random breakages.

How Has This Been Tested?

Yes, using pip-sync.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have read the CONTRIBUTING document.

deathaxe commented 10 months ago

What's the reason for this?

I've never experienced issues with currently rolling releases and don't actually want to start bothering about versions.

mataha commented 10 months ago

What's the reason for this?

Recommended workflow for managing and generating requirements files; I admit I got cut on installing black once.

I've never experienced issues with currently rolling releases and don't actually want to start bothering about versions.

This is likely a one-time thing. There's no need to be bothered.

mataha commented 5 months ago

I still think there's value in pinning dependencies, especially when working with locally installed Python versions that differ from system-wide ones (e.g. I mainly use 3.12, but Sublime packages obviously require 3.8).

That said, it's not a hill I would like to die on - I've given up on trying to manage Python dependencies in a sane way and have since moved to greener pastures.

SublimeText / AFileIcon