Re:Analyzing Django requirement files on GitHub
by rbanffy on Thursday June 08, 2017 @11:51AM
(#14515020)
I tend not to pin versions. When I generate requirements files, I use pip-chill (disclaimer: I made it) to avoid listing redundant dependencies.
[ Parent
| on HN ]
Re:Analyzing Django requirement files on GitHub
by Alex3917 on Thursday June 08, 2017 @11:55AM
(#14515051)
Interesting. To me pip-tools seems like a better fit for this use case, in terms of letting you specify a requirements.in file that gets compiled to a requirement.txt file. This allows you to selectively pin dependencies of other packages if you have some use case for doing so.
Something related that would be nice though is having pip list -o only output dependencies in the requirements.in file if it exists, or else that are primary dependencies.
Re:Analyzing Django requirement files on GitHub
by rbanffy on Thursday June 08, 2017 @04:21PM
(#14516906)
You can tell it to generate the list without version numbers so you can get a clean requirements.in for pip-tools to compile.
Re:Analyzing Django requirement files on GitHub
by jijojv on Thursday June 08, 2017 @11:58AM
(#14515079)
I didn't use to pin versions until last weekend i experienced https://pypi.python.org/pypi/requests going through 15 revs within 3 days.
Re:Analyzing Django requirement files on GitHub
by rbanffy on Thursday June 08, 2017 @06:41PM
(#14517724)
I say I tend. I never said I never do it. ;-)
My development environment is not pinned. When I set up CI, I do it with bot pinned (as it goes to production) and unpinned (from dev) requirements, both generated using pip-chill.