All commit authors signed the Contributor License Agreement.

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

You need to sign the CLA.

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

Sorry, @vict-Yang and @picnixz, I could not cleanly backport this to 3.14 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker ce70a57bc02fddc8cb18a08aaf1449fceb10d66e 3.14

Sorry, @vict-Yang and @picnixz, I could not cleanly backport this to 3.13 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker ce70a57bc02fddc8cb18a08aaf1449fceb10d66e 3.13

Of course. The backports.

@vict-Yang are you interested in making the backports PR (https://devguide.python.org/getting-started/git-boot-camp/#backporting-merged-changes) or do you want me to do it?

We should improve Miss Islington to update them.

git itself fails to cleanly merge the commit without conflicts so I don't think we should do something smarter. It's sometimes very hard to decide how to solve conflicts (sometimes it's more than just selecting what needs to be selected).