Python 3.13 is now in the release candidate (RC) stage and that means:
A branch preparing for an RC release can only have bugfixes applied that have been reviewed by other core developers. Generally, these issues must be severe enough (for example, crashes) that they deserve fixing before the final release. All other issues should be deferred to the next development cycle, since stability is the strongest concern at this point.
While the goal is to have no code changes between a RC and a final release, there may be a need for final documentation or test fixes. Any such proposed changes should be discussed first with the release manager.
You cannot skip the peer review during an RC, no matter how small! Even if it is a simple copy-and-paste change, everything requires peer review from a core developer.
https://devguide.python.org/developer-workflow/development-cycle/#release-candidate-rc
Please make sure that everything going into the 3.13
branch is peer reviewed.
We don’t yet have any automation to enforce this, but we plan to add it in September. Until then, please remember to request a review from another core team member.
We’ve discussed requiring reviews in general (2020, 2023, 2024), so this will be a good trial for that.
Thanks!