Core Dispatch #2

Welcome back to Core Dispatch! This edition covers April 4–16, 2026, and there's a lot going on. As expected, new releases are out for 3.13, 3.14, and 3.15. Python 3.15.0 beta 1 is right around the corner (May 5), and if you've got PRs you want in 3.15, now's the time! Feature freeze is less than 3 weeks away. Don't miss the window, otherwise it'll go into 3.16 and have to wait until October 2027 for release.

The incremental GC introduced in 3.14 is being reverted due to memory pressure in production environments. Python 3.14 and 3.15 will return to the previous generational GC.

The Steering Council has accepted a number of PEPs, including PEP 772, which establishes a new Packaging Council!

Łukasz Langa is stepping down as the PSF's first CPython Developer in Residence after nearly five years. Thank you, Łukasz (we know where to find you)!

Emma Smith published a Rust for CPython progress update: the build system now works across all CI platforms, and the team has shifted their target from 3.15 to 3.16 to give more time for API design and a PEP. If you're attending PyCon US and interested in Rust for CPython, Emma will be giving a talk on the initiative and there will also be a sprint on the topic.

CPython is moving platform-specific build files to the new Platforms/ directory. Most of the platforms have been migrated, with the rest planned to be moved prior to 3.15 beta 1. If you build CPython, you'll want to update your automation so it is ready for beta 1!

If you maintain a package or just like living on the edge, make sure to give the latest 3.15 alpha a spin and file any issues you find.