New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

requirements.txt should not be frozen, instead add a frozen requirements.txt #8

Open

ronreiter opened this issue Feb 16, 2020 · 3 comments

ronreiter commented Feb 16, 2020 •

edited

Loading

https://www.kennethreitz.org/essays/a-better-pip-workflow

This is important because sometimes requirements break due to cascading dependency requirements failure.

Owner

saasforge commented Feb 20, 2020

This is an interesting approach. Can you provide its implementation and a guide on how to use it?

Author

ronreiter commented Feb 25, 2020

Just need to keep requirements.txt as the raw requirements and requirements-frozen.txt as the frozen ones.

https://medium.com/@tomagee/pip-freeze-requirements-txt-considered-harmful-f0bce66cf895

Author

ronreiter commented Feb 25, 2020

BTW, Pipfile.lock is kind of a similar mechanism:
https://pipenv-fork.readthedocs.io/en/latest/basics.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment