A friendly reminder: tomorrow is the scheduled date for Python 3.13.0 rc2 (the last release candidate). If the macOS thin-lto performance issues get sorted out by @nad (which looks to be the case), it should happen on schedule. I plan to lock the branch for the release and then keep it locked until the final 3.13.0 release.
If you have any bugs you think should be fixed in 3.13.0 (not just rc2), or any PRs that should go into 3.13.0, let me know now.
If you run into any bugs or PRs you think canāt wait for 3.13.1 after rc2 has been cut, let me know and weāll figure out how to address it together.
After talking with @ambv (who just came back from vacation) about some of the pending pyrepl issues he would like to fix before rc2, weāve decided to push 3.13.0rc2 to this Friday, September 6, instead.