[strokirk]

CI providers should definitely start proxying PyPI with their own cache.

[Numerlor]

I wanted to spin up a mirror locally to do simple caching for docker builds but the tooling was lacking, there was a way to do a direct mirror of pypi locally but no other way of adding custom indices

[jeroenhd]

I think Sonatype Nexus [1] can do that relatively easily. I don't know if the OSS version is enough, but I think most people and projects should be fine.

[1]: https://www.sonatype.com/products/sonatype-nexus-oss-downloa...

[TheChaplain]

DevPi might be your answer I think. Couple of years ago I set it up as a proxy plus hosting my own packages locally.

[0x138d5]

Artifactory?

[zahlman]

Pip already does its own caching, but it's maddeningly difficult to even locate and extract files, let alone set up anything usable. It's also needlessly difficult to make Pip just use such a cache directly - for example, if you haven't pinned a version, it will automatically check PyPI to figure out the latest version even if you have cached wheels already.

I don't know (I lack the experience), but I assume that container systems get in the way of Pip finding its normal cache, too. (If they're emulating a filesystem or something, then the cache is in the wrong filesystem unless you reuse the container.)

[Spivak]

It might honestly be easier and cheaper for those CI providers to just pay PyPI's bandwidth costs.