bazelbuild
feat(pip): global downloader settings
Initial API proposal for a stable API for the experimental_index_url.
TODO for this PR:
- [ ] Agree on the interface and flow - it should be described either as a sketch in docs in how to or in the attributes.
- [ ] Implement
- [ ] Deprecation messages for the
experimental_*index*flags
WIP
#2951
@dougthor42, could you please comment on how you imagine the API work for the downloader configuration?
airlock has soak time
My day team has run into something similar.
A release candidate will be created, but its hard to consume unless its also uploaded to pypi. Similarly, various projects are wired up to use nightly wheels of important dependencies. Right now, this works by using file:// in requirements files and some repo-rule pre-processing.
package migrated from index a to index b
iirc, my day team had to change the GCS buckets wheels were being uploaded to. There were a lot of old wheels, and it was generally a pain, so they only copied over recent releases and left the old ones sitting there. The net effect is a partial index based on version. I think this is really niche, though, so don't think its worth trying to add foo >1.0 support in the override logic.
