[Python-Dev] PEP 453 Round 4 - Explicit bootstrapping of pip in Python installations
ncoghlan at gmail.com
Thu Sep 19 16:05:26 CEST 2013
On 19 Sep 2013 23:53, "Antoine Pitrou" <solipsis at pitrou.net> wrote:
> Le Thu, 19 Sep 2013 09:27:24 -0400,
> Donald Stufft <donald at stufft.io> a écrit :
> > We've updated PEP453 based on some of the early feedback we've gotten
> > from -dev and Martin.
> > Major changes:
> > * Removal of the option to fetch pip from PyPI in order not to modify
> > the trust model of the Python installers
> > * Consequently rename the model from ``getpip`` to ``extractpip``
> "ensurepip" ?
Oh, I like it - describes exactly why the module exists :)
> What happens if there is already a higher pip version installed?
> I suppose "extractpip" doesn't do anything in that case?
> (sorry, perhaps it's mentioned in the PEP and I haven't seen it.
> The PEP has become so long that I've only skimmed through it.)
As Donald said, the fact nothing happens in that case is currently only
implied by the fact this is the way pip's "--upgrade" option works.
We should make that explicit in the PEP.
> Python-Dev mailing list
> Python-Dev at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev