gh-103559: Update bundled pip version to 23.1.1 #103560
Conversation
|
We'll be releasing a 23.1.1, so I will update this PR once that happens, rather than creating a new PR. |
Cool. Ping me if I don't give you an approval quickly. Also, do you want me to merge it, automerge it, or leave it to you (if you can)? I haven't tested it but I believe this will help unblock #98040 and #98573 |
|
@warsaw I'm fine with merging myself once the release is done, and I think it's uncontroversial enough that I won't bother waiting for you to re-approve (unless you'd prefer that I did). I'll try to get the pip release done tomorrow (UK time). |
|
Sounds good @pfmoore - I'll leave it to you. I agree it's uncontroversial. And thanks! |
|
Sorry, @warsaw, we've just found a further issue that needs to be included in pip 23.1.1. Would it help you if I merged this PR now, on the understanding that there will be a subsequent PR upgrading to 23.1.1? It's not much extra work, so if it's useful to you, just let me know. |
|
Thanks @pfmoore for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11. |
|
Sorry, @pfmoore, I could not cleanly backport this to |
|
@pradyunsg It appears that #95299 was not backported to Python 3.11. Is that intentional, or simply an oversight? As it stands, that makes it messy to backport this PR to 3.11. What is the expectation regarding 3.11? To be explicit:
|
pradyunsg
changed the title
|
GH-103752 is a backport of this pull request to the 3.11 branch. |
* Update bundled pip version to 23.1 * Update to pip 23.1.1 (cherry picked from commit b286295)
|
Never mind, fixing the backport wasn't too hard, so I did it. #95299 can be dealt with however you prefer. |
…103752) (cherry picked from commit b286295) Co-authored-by: Łukasz Langa <[email protected]>
closes: #103559
x-ref: pypa/pip#11902