[21:25:26] <wilornel__> At work we are using Jenkins for CI internally and Travis CI externally. I see that our jobs are basically doing `virutalenv env; pip install -r requirements.txt`, which downloads all of these packages. In the case of the internal CI, it downloads the packages from our internal repos.
[21:26:32] <wilornel__> However, I feel like no downloading might be necessary... I feel like it should be possible to keep these dependencies in the fs, and tell pip to "hide" all dependencies before running `pip install -r requirements.txt`, which would show a dependency if it is hidden, and download it if it does not exist..
[21:27:07] <dstufft> wilornel__: fwiw modern pip's will aggresively cache things automatically so that it doesn't need to constantly redownload
[21:27:21] <wilornel__> I just tried it on my dev server, and I can just rename the package directory: `mv /home/me/proj/env/lib/python2.7/site-packages/Fabric-1.11.1-py2.7.egg-info{,.old}`
[21:27:38] <wilornel__> dstufft: Makes sense. Does it have to reinstall them though?
[21:28:42] <dstufft> wilornel__: yea it does, though if you have ``wheel`` installed in your virtualenv reinstallation is very fast too, as the first time it installs it will build a wheel file (which is a binary package and is essentially just a zip file) and will install from that (essentially just an unzip + mv)