News for hackers. Stuff that matters.
Re:Should You Use Upper Bound Version Constraints (In Python)? by globular-toast on Wednesday April 17, 2024 @03:51AM (#40061685)
This is what I do:

1. Use pip-tools to generate a pinned requirements list. This is used to build artifacts like docker images, installer bundles etc. All pins are upgraded periodically (manually). Any version changes are inspected (this requires "knowing" your dependencies a bit and which ones might cause problems). Finally the resulting artifacts are manually tested.

2. An automated build of master every 24 hours from completely unpinned versions. That is installing the package fresh from pyproject.toml. The automated test suite will reveal any upcoming breakage that would happen if we continue without upper bounds on certain packages. If there is breakage we decide whether to accommodate the new breaking dependencies or constrain them with an upper bound (perhaps recording a tech debt).

Re:Should You Use Upper Bound Version Constraints (In Python)? by ijustlovemath on Wednesday April 17, 2024 @11:13PM (#40072606)
So you keep two requirements.txt files?
Re:Should You Use Upper Bound Version Constraints (In Python)? by globular-toast on Thursday April 18, 2024 @02:52AM (#40073624)
Not exactly. Look up how pip-tools works.