This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pradyunsg
Recipients Marcus.Smith, brett.cannon, dstufft, ncoghlan, ned.deily, paul.moore, pradyunsg
Date 2019-11-05.13:05:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAPA-EqsPQ+snzPSF5pY9-SUMDj4gdHyrkP0N91QqR5j68JLZ0w@mail.gmail.com>
In-reply-to <1572951627.08.0.00218421202038.issue38662@roundup.psfhosted.org>
Content
On Tue, 5 Nov 2019 at 4:30 PM, Ned Deily <report@bugs.python.org> wrote:

>
> Ned Deily <nad@python.org> added the comment:
>
> Can you explain how this would be rolled out?

This, as in? If you're referring to this specific change, I don't think
there's anything special needed for this change (it's backwards compatible
with past pip releases, but that doesn't matter).

ensurepip only installs the bundled wheel it already has, into the
environment. Thus, existing ensurepip releases won't be broken.

However, when we bump up to pip 19.3 [1], we'd need to be updating the
invocation since it's using a pip internal and pip's internals can change
without notice even in a patch version.

This change ensures that ensurepip is robust to changes in the location of
pip's main function, thus making those updates as simple as a bundled wheel
change.

[1]: IIUC we try to keep CPython's bundled wheel in sync with latest)

Does this mean as of a planned release of pip the current ensurepip would
> break?

Yes. pip 19.3 made a change and as can be seen in the PR for that (sorry,
it's a GitHub PR and my internet is ridiculously slow right now).

  If so, when?

That's already been released. 🙃

Is 2.7 still supported with that version of pip and, if so, have you tested
> the PR with it?

Yes, pip will support 2.7 at least until CPython does (and likely longer).

>
> ----------
> nosy: +ned.deily
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue38662>
> _______________________________________
>
History
Date User Action Args
2019-11-05 13:05:26pradyunsgsetrecipients: + pradyunsg, brett.cannon, paul.moore, ncoghlan, ned.deily, dstufft, Marcus.Smith
2019-11-05 13:05:26pradyunsglinkissue38662 messages
2019-11-05 13:05:25pradyunsgcreate