News for hackers. Stuff that matters.
Re:Learning Go as a Python Developer: The Good and the Bad by paulsef11 on Monday July 18, 2022 @04:47PM (#32143449)
There's lots of cases where you wouldn't want to pin your requirements.txt, the main one being if you're authoring a package. You need to leave the versions unpinned, preferably just bound to a major version, allowing some variability for the users of your package in case there's a shared dependency. I have a feeling that's what the author is describing here, because Poetry solves this dilemma by introducing a poetry.lock file which pins the dev versions of all the dependencies, but publishes a package with unpinned deps.

There are no comments on this comment yet.