> On Oct 14, 2015, at 1:04 PM, Donald Stufft <don...@stufft.io> wrote: > > Generally within 60-120 seconds it’s available in mirrors (most of them > resync once a minute). If anyone has downloaded it then they will have pretty > much permanently cached the package, first in the download cache and then > again in the wheel cache (assuming it wasn’t a wheel already, and they had > that enabled). The original package was NumPy. It had 30,982 downloads in the > last day, so we can average that out to 1290 downloads an hour or 21 > downloads a minute. If it takes you two minutes to notice it and delete it, > then there are ~40 people who already have the original version cached and > who will not notice the updated version.
While I don't think PyPI should allow modification of uploaded packages necessarily, I do think that Pip's caching is (A) too aggressive and (B) too opaque. For example: https://github.com/pypa/pip/issues/3127 https://github.com/pypa/pip/issues/3034 https://github.com/pypa/pip/issues/3025 https://github.com/pypa/pip/issues/2908 https://github.com/pypa/pip/issues/2882 etc, etc. I know there are some directories platform-specific directories I can delete, but almost once a day I want a command like `pip cache show´ which can show me what is cached and when/where it was built, `pip cache clear´ or `pip cache remove twisted´ or `pip cache remove cffi>=1.0´. I don't want to have to care if it's in the HTTP cache or the wheel cache, or how it got there; I also don't want to have to bust a ~200 megabyte cache that saves me hours a day just because there's one bad entry in there. -glyph
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
