This one is not specific of django but it is very common during the development of any python project. Managing the contents of the requirements.txt file, that sometimes grows uncontrollably can be a mess. One of the root causes is the common work-flow of using virtualenv, install with pip all the required libraries and then do something like:
$pip freeze > requirements.txt
At the beginning this might work great, however soon you will need to change things and remove libraries. At this point, things start to get a little trickier, since you do not know which lines are a direct dependency of your project or if they were installed because a library you already removed needed them. This leads to some tedious work in order to maintain the dependency list clean.
To solve this problem we might use pip-tools, which will help you declare the dependencies in a simple way and automatically generate the final requirements.txt. As it is shown in the project readme, we can declare the following requirements.in file:
django requests pillow celery
Then we generate our “official” requirements.txt with the pip-compile command, that will product the following output:
# # This file is autogenerated by pip-compile # Make changes in requirements.in, then run this to update: # # pip-compile requirements.in # amqp==1.4.8 # via kombu anyjson==0.3.3 # via kombu billiard==3.3.0.22 # via celery celery==3.1.19 django==1.9 kombu==3.0.30 # via celery pillow==3.0.0 pytz==2015.7 # via celery requests==2.8.1
Now you can keep track of where all those libraries came from. Need to add or remove packages? Just run pip-compile again.
