sunlightlabs/brisket — comment on commit 74d8c2c79c4d3b56ba6b8734cc2204a8f78e1e74
File:  line 0
By arowla:

Feel free to add it back in if you can diagnose what was wrong. However, requirements.txt , AFAIK, has never been totally canonical as far as packages that we require. A few of our packages, such as saucebrush, have long lived as bare git repos in /home/datacommons/lib/python/, with their directories included in our virtualenv via virtualenv_path_extensions.pth. Doing a git pull on those is a straightforward way to update them. Certainly, if things remain this way, the README should be updated and expanded to fully document the upgrade process.

We've had cases where a pip upgrade had us end up with two separate copies of the package source included in our project, which is confusing and wrong to say the least. I haven't had the time to figure out the exact interplay between pip, setuptools and virtualenv enough to get it straightened out. It would be great if we could get it fixed, though.