[Distutils] PEP 453 Round 2 - Explicit bootstrapping of pip in Python installations

[Nick Coghlan]

On 17 September 2013 12:21, Donald Stufft <donald at stufft.io> wrote:
>
> On Sep 16, 2013, at 10:15 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
>
>> However, I just noticed that the PEP *doesn't* currently specify the
>> effect of running "python -m getpip" when pip is already installed. I
>> believe it should attempt to upgrade pip, so that in the normal course
>> of events (i.e. just installing CPython maintenance releases without
>> manually upgrading pip), then pip will be automatically upgraded to
>> the latest version each time CPython itself is updated.
>
> TBH I just assumed it would say that pip is already bootstrapped, but I'm
> OK with making it upgrade as well. My thinking was if you already had
> pip then ``pip install --upgrade pip`` is easier but making the bootstrap
> upgrade too does mean that installing a maintenance release will upgrade
> your pip too which is kinda nice.

Yeah, that's the exact same thought process I went through :)

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia