saasforge/open-source-saas-boilerpate

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

ronreiter opened this issue · 3 comments

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

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

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

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

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