"--package-cache" #878
"--package-cache" #878
Comments
a good mailing list thread on the |
+1, I think this becomes even more useful with wheel support. I think it would be useful when using download cache to have packages get moved (with new name scheme) from download-cache -> package-cache, but if both are enabled, only store new downloads in package-cache. Also would be good to have a "prune-cache" command that can go through and delete older versions - of course you may want to keep older versions, but the prune option can just cover the common case. |
In this thread, I'm agreed with Marcus Smith proposal. |
Will a wheel archive be created for all installed package ? |
not the way this was written up originally (this was pre-wheel thinking). |
Have you already started to work on implementation of this feature ? |
@qwcode ping |
no |
Ok, I'll may be work on this feature… |
This feature --package-cache, especially combined with --build-wheel, would be a very useful addition to pip, and ease a lot of deployment scenario. |
A thousand times yes! This will also make multi-project handling easier. How about a way of installing a package from the file system into the cache? For example, after building a wheel with 'python setup.py bdist_wheel' I'd like to be able to add the generated wheel to the cache, either automatically (controlled via feature) or manually (custom pip command?). I guess 'pip install -e . --build-wheel' could be used to accomplish this using the last bullet point. |
Going to close this, as it's now done(ish)! |
this was discussed in broad terms at pycon with @dholth and @jezdez
here's the text from a gist I posted months ago. reposting it as a real issue to get discussion at some point. not sure when this would land in an actual milestone to be worked on.
"--package-cache"
(if the req was "nose", any nose version in the package-cache would "win", unless --upgrade is specified)
The text was updated successfully, but these errors were encountered: