Can you please target your PR to the main branch? That's where all PR are merged so they are never lost for future versions, you don't want this paragraph to reappear in 3.12.

To hit 3.11 we backport PRs on main to 3.11 (using a bot reading github labels).

(Sorry for the big flood or Github automated reviews! I just tried to base the PR on main from the Github UI, hoping it would work as the commit was simple...).

PRs attempting to merge a maintenance branch into the main branch are deemed to be spam and automatically closed. If you were attempting to report a bug, please go to bugs.python.org; see devguide.python.org for further instruction as needed.

Sorry, I don't know why I targeted 3.11, the habit of the translation workflow I guess. To avoid a big pile of unrelated commit and still use the same PR, I created a branch from an up-to-date main named 3.11 and force-pushed it to my (old) 3.11 remote , but it mysteriously upset'd bedevere bot who close my PR. If you can't reopen it, I will create another.

If you can't reopen it, I will create another.

Creating another would be the best course of action here! It's basically impossible to change the target branch on a CPython PR without causing a huge flood of review requests for loads of people, unfortunately.