Closed danparizher closed 10 months ago
I do not really see the use in this? You can just pip install -r and you're ready to go?
I do not really see the use in this? You can just pip install -r and you're ready to go?
If a package is removed from the requirements file, it will not be removed from your venv. Piptools fixes that issue by syncing your venv exactly with what is needed in your environment
I do not really see the use in this? You can just pip install -r and you're ready to go?
If a package is removed from the requirements file, it will not be removed from your venv. Piptools fixes that issue by syncing your venv exactly with what is needed in your environment
Do I need to use this? Or can I just do it the normal way if I prefer to?
No you don't have to, you can use pip install -r requirements.txt
like you always have. It just helps with granularity. It shouldn't really affect anyone's workflow
We can use
pip-tools
to use commands likepip-sync
andpip-compile
. Basically, we would have a new file calledrequirements.in
which would house the packages we would normally have inrequirements.txt
. After compiling it, it will autogenerate all nested dependencies torequirements.txt
, whichpip-sync
can then read and sync with your environment.