[Distutils] What to do about the PyPI mirrors

[Donald Stufft]

Okies I can write one up. 

On Aug 4, 2013, at 5:45 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:

> On 4 August 2013 19:18, Donald Stufft <donald at stufft.io> wrote:
>> 
>> On Aug 4, 2013, at 5:13 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
>> 
>>> On 4 August 2013 18:48, Donald Stufft <donald at stufft.io> wrote:
>>>> 5 days ago my branch to remove mirroring support from pip was merged into pip's develop branch. I don't see any direct support for mirroring in setuptools nor do I see any in buildout so I think it makes sense to hold off on the final deletion until after the only of the 3 major installers that seems to have any direct support for mirrors has released a version without it plus a bit of lead time for people to switch.
>>>> 
>>>> So I guess revised I'd say in roughly two months on Oct 1st the [a-g].pypi.python.rg DNS names will be redirected to front.python.org and then roughly 2 months after pip has released version 1.5 with the removal of the mirroring support they will be deleted along with last.pypi.python.org.
>>> 
>>> Sounds good to me. You may not love this next part though: since the
>>> mirror naming scheme was originally defined in a PEP
>>> (http://www.python.org/dev/peps/pep-0381/#mirror-listing-and-registering),
>>> I think its retirement should also be published that way.
>>> 
>>> The PEP doesn't need to be long, it should just say that PyPI will
>>> continue to support the mirroring protocol (and perhaps even mention
>>> that the current preferred mirroring tool is bandersnatch rather than
>>> pep381client), but the CDN is considered to replace the public mirror
>>> network and those DNS names will all be retired.
>> 
>> OTOH that PEP was never accepted and is currently a draft
> 
> Alas, the nominal status of the packaging PEPs isn't always a great
> guide to their real world usage :P
> 
>> but if you really
>> think it should be a PEP I can write one up.
> 
> I think we're at a point where overcommunicating is definitely better
> than the alternative :)
> 
> In this case, what I suggest we do is put the new PEP to Accepted with
> a Replaces: header for 381, and then set 381 to Superseded.
> 
> Cheers,
> Nick.
> 
> -- 
> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia