[issue33131] Upgrade to pip 10 for Python 3.7

Change by Nick Coghlan : -- assignee: -> paul.moore resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue33131] Upgrade to pip 10 for Python 3.7

miss-islington added the comment: New changeset 47d57bfd3d6ceb08f98fcff14fe3c8bb41ca0664 by Miss Islington (bot) in branch '3.6': bpo-33131: Upgrade ensurepip to bundle pip 10.0.1 (GH-6546) https://github.com/python/cpython/commit/47d57bfd3d6ceb08f98fcff14fe3c8bb41ca0664 --

[issue33131] Upgrade to pip 10 for Python 3.7

miss-islington added the comment: New changeset 4caba7a94024d8af2eed26300f13ff4433dcb05b by Miss Islington (bot) in branch '2.7': bpo-33131: Upgrade ensurepip to bundle pip 10.0.1 (GH-6546) https://github.com/python/cpython/commit/4caba7a94024d8af2eed26300f13ff4433dcb05b --

[issue33131] Upgrade to pip 10 for Python 3.7

miss-islington added the comment: New changeset b221107d32370670905fefb569b3104748f92afe by Miss Islington (bot) in branch '3.7': bpo-33131: Upgrade ensurepip to bundle pip 10.0.1 (GH-6546) https://github.com/python/cpython/commit/b221107d32370670905fefb569b3104748f92afe -- nosy: +mi

[issue33131] Upgrade to pip 10 for Python 3.7

Change by miss-islington : -- pull_requests: +6249 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue33131] Upgrade to pip 10 for Python 3.7

Ned Deily added the comment: Since 2.7 was upgraded, I think 3.6.x should be upgraded to 10.0.x, as well. -- versions: +Python 2.7, Python 3.6 ___ Python tracker ___ __

[issue33131] Upgrade to pip 10 for Python 3.7

Change by miss-islington : -- pull_requests: +6248 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue33131] Upgrade to pip 10 for Python 3.7

Change by miss-islington : -- pull_requests: +6247 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue33131] Upgrade to pip 10 for Python 3.7

Paul Moore added the comment: New changeset 0399cf9b5e370516e3d0aed6a63ff74aff5eadb5 by Paul Moore in branch 'master': bpo-33131: Upgrade ensurepip to bundle pip 10.0.1 (GH-6546) https://github.com/python/cpython/commit/0399cf9b5e370516e3d0aed6a63ff74aff5eadb5 -- ___

[issue33131] Upgrade to pip 10 for Python 3.7

Change by Paul Moore : -- keywords: +patch pull_requests: +6243 stage: needs patch -> patch review ___ Python tracker ___ ___ Python-

[issue33131] Upgrade to pip 10 for Python 3.7

Ned Deily added the comment: The ensurepip blob is a bit of a special case regarding updates, that is, I think we can be a little more flexible about them since they are getting tested and a lot of exposure external to Python releases. Accepting a bugfix update for pip between 3.7.0b4 and 3.

[issue33131] Upgrade to pip 10 for Python 3.7

Paul Moore added the comment: Thanks Nick, that's what I thought for the workflow. And agreed with your understanding of the post-b4 question, but as you say Ned's the boss on that one :-) -- ___ Python tracker

[issue33131] Upgrade to pip 10 for Python 3.7

Nick Coghlan added the comment: Merge to master and set the "needs backport to 3.7" label for the initial PR - the backport bot will then take care of creating the 3.7 PR. For the backport, all you then need to do is leave an Approve review, and the bot will automatically merge it once the CI

[issue33131] Upgrade to pip 10 for Python 3.7

Paul Moore added the comment: Pip 10 has now been released. I'll be getting a PR to put it into 3.7 in the next few days. One question on workflow - is the right approach to create a PR for master and request a backport to the 3.7 branch? Or is there something else I should do? Also, can I j

[issue33131] Upgrade to pip 10 for Python 3.7

Ned Deily added the comment: The changelog for a release is our primary notification to users about what has changed in a Python release. With 3.6.5, we just had a case where it seemed important to update pip between the release candidate and the final, something we normally would not do. I

[issue33131] Upgrade to pip 10 for Python 3.7

Nick Coghlan added the comment: It's a useful data point for folks trying to diagnose post-maintenance-update failures when we upgrade pip on their behalf, rather than them explicitly doing it themselves. -- ___ Python tracker

[issue33131] Upgrade to pip 10 for Python 3.7

Donald Stufft added the comment: Oh, I had never written NEWS entries for upgrading pip/setuptools, with the idea that the specific version being installed is considered an implementation detail. However if folks want it, I can. -- ___ Python track

[issue33131] Upgrade to pip 10 for Python 3.7

Ned Deily added the comment: BTW, when updating the bundled wheels, please remember to use an issue (like this one) and include a NEWS entry using blurb; in other words, don't use the "skip news" label on PRs. That way the change will be documented in the Misc/NEWS and docs changelog.html fo

[issue33131] Upgrade to pip 10 for Python 3.7

Nick Coghlan added the comment: Possibly - we implemented ensurepip the way we did just because it was the easiest option, not because we closely considered all the available approaches. That would be a separate process improvement issue, though :) --

[issue33131] Upgrade to pip 10 for Python 3.7

Serhiy Storchaka added the comment: Currently the repository contains blobs for pip and setuptools (2 MB total) which are updated with every release of pip and setuptools. This increases the size of the repository by 2 MB several times per year. Wouldn't be better to put them in a separate re

[issue33131] Upgrade to pip 10 for Python 3.7

New submission from Nick Coghlan : Paul brought up recently [1] that with pip 10.0.0 due for release next month [2], we'd really prefer to ship that in Python 3.7.0 (such that 3.7 launches with PEP 518/517 pyproject.toml support), rather than shipping with 9.0.x and then upgrading to 10.0.0 in