Paul Moore

@ncoghlan can you clarify? Surely PyPI will always disallow uploads with *whatever* tag we decide on, and the remaining 3 points don't seem in any way linked to the choice...

> Perhaps there is a case to be made for two tags? ("local" for the implicit cache, "custom" for explicit overrides) That seems over-complicated. Unless you're thinking of something more...

> 'local' overrides everything except 'custom'. It is used implicitly by the wheel cache to get locally built wheels to take precedence over pre-built remote archives. First of all, why...

I don't think I said that caching wouldn't use "local". Just that if it did, and didn't match any other "local" build, then someone's building things wrongly. Maybe we're talking...

> But perhaps it is a sign that custom should be defined as a tag prefix We've established that we require a PEP for this change. I think that a...

I imagine pip would do whatever packaging supports. I'm not at a PC where I can do this right now, but can't you just check by doing something like `pip...

I should note that I'm also not sure packaging is the right home for this. I used packaging purely as a placeholder for "not pip", as I definitely don't think...

I'm assuming that https://bootstrap.pypa.io would remain unchanged, as that's where get-pip.py and the virtualenv zipapp version is hosted. I imagine that is hard coded in a *lot* of places, so...

> This might be a minority opinion, but I'm a strong -1 on all the changes proposed here. I'm -0 myself to be honest, so you're not a complete minority...

Typically any attempt to recommend a preferred solution is met with debate. There really doesn't seem to be a consensus. FWIW, if I recall the common objection to the approach...