Note that 3.14 is in RC-mode,@hugovk may reasonably want to defer backporting this to 3.14.1 -- but by then, I expect a new version ofpip will have been released.

A

Let's backport when ready: this will get wide exposure in 3.13.6 (2025-08-05) before 3.14.0 RC2 (2025-08-26).

Thanks!

I'm not sure how this could be out of date with main? Maybe the news files? Does anyone know a good reason why Ishouldn't just hit "Update branch"?

@ichard26 ping me when you are ready for this to be merged, and I'll set the merge going and do the backports. For information, we bacport new versions of pip to all currently maintained Python versions. And as in this case, if we're in the beta or RC period, we should get RM approval. As@hugovk has approved, we're good on that point.

I'm not sure how this could be out of date with main? Maybe the news files? Does anyone know a good reason why Ishouldn't just hit "Update branch"?

It's a somewhat-unhelpful message, this branchis indeed behind, but not for anything that matters (hence no 'resolve conflicts' message). Clicking the button doesn't hurt, but triggers a full CI rerun, so generally best avoided. It can be helpful when the problem is with CI itself, though.

A

Let's backport when ready: this will get wide exposure in 3.13.6 (2025-08-05) before 3.14.0 RC2 (2025-08-26).

It's been all quiet on thewestern post-release front so far (and I doubt we're going to discover any show-stopping bugs at this point) so let's get this merged now so it can be battle tested via Python 3.13.6. cc@pfmoore

Thanks@ichard26 for the PR, and@ZeroIntensity for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14.
🐍🍒⛏🤖

GH-137361 is a backport of this pull request to the3.14 branch.

GH-137362 is a backport of this pull request to the3.13 branch.

⚠️⚠️⚠️ Buildbot failure⚠️⚠️⚠️

Hi! The buildbotAMD64 Windows Server 2022 NoGIL 3.14 (tier-1) has failed when building commit127ec30.

What do you need to do:

1. Don't panic.
2. Checkthe buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1717/builds/448) and take a look at the build logs.
4. Check if the failure is related to this commit (127ec30) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1717/builds/448

Failed tests:

• test_launcher

Failed subtests:

• test_search_major_3 - test.test_launcher.TestLauncher.test_search_major_3
• test_search_major_2 - test.test_launcher.TestLauncher.test_search_major_2

Summary of the results of the build (if available):

==

Traceback (most recent call last):  File"C:\Users\Administrator\buildarea\3.14.itamaro-win64-srv-22-aws.x64.nogil\build\Lib\test\test_launcher.py", line465, intest_search_major_2self.assertEqual("PythonCore", data["env.company"])~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^AssertionError:'PythonCore' != 'PythonTestSuite'- PythonCore+ PythonTestSuiteTraceback (most recent call last):  File"C:\Users\Administrator\buildarea\3.14.itamaro-win64-srv-22-aws.x64.nogil\build\Lib\test\test_launcher.py", line445, intest_search_major_3self.assertEqual("PythonCore", data["env.company"])~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^AssertionError:'PythonCore' != 'PythonTestSuite'- PythonCore+ PythonTestSuite