Editions
Every edition of Core Dispatch.
Core Dispatch #4
Apr 30 – May 18, 2026
Welcome back to Core Dispatch! This edition covers April 30 through May 18, 2026. Python 3.15.0 beta 1 is officially here, which means CPython's `main` branch is now open for 3.16 work. The first 3.16 alpha is slated for mid-October. More imminently, beta 2 is up next on June 2, with 3.13.14 and 3.14.6 following on June 9. This is also PyCon US week, so a lot of the core team is gathered in Long Beach right now. Once recordings are available, we'll be sure to pull talks from folks on the team into a future edition. PEP 788 has also moved from accepted to implemented, and free-threaded builds picked up thread-safe iterator support. There are also a few smaller but concrete fixes: `http.server` can send custom headers from the command line, `AttributeError` can suggest Python equivalents for method names from other languages, `webbrowser` on macOS is moving away from `osascript`, and `ftplib.ftpcp()` picked up the PASV CVE fix. If you maintain a package or just like living on the edge, give the latest 3.15 beta a spin and [file any issues](https://github.com/python/cpython/issues) you find.
Core Dispatch #3
April 16 – 30, 2026
Welcome back to Core Dispatch! This edition covers April 16–30, 2026. Python 3.15.0 beta 1 is just around the corner (that's next week...but who's counting?). If you've got outstanding features, now's the time, or else you'll have to wait for 3.16.0! Heads up: there's also an early 3.14.5 next week. 3.14.5rc1 ships Saturday May 2 with the final on Friday May 8, pulled forward to deliver the [incremental GC revert](https://discuss.python.org/t/reverting-the-incremental-gc-in-python-3-14-and-3-15/107014) we mentioned last edition. The Steering Council was busy. [PEP 661](https://peps.python.org/pep-0661/) was accepted after nearly five years of discussion. [PEP 788](https://peps.python.org/pep-0788/), [PEP 820](https://peps.python.org/pep-0820/), [PEP 829](https://peps.python.org/pep-0829/), and [PEP 831](https://peps.python.org/pep-0831/) also got the green light, while [PEP 708](https://peps.python.org/pep-0708/) and [PEP 806](https://peps.python.org/pep-0806/) were turned down. Big fortnight on the PEP front! It's also a great time to review the 3.15 [What's New](https://docs.python.org/3.15/whatsnew/3.15.html) to see what's coming in the next release (spoiler: it's a lot of really cool stuff). As always, if you maintain a package or just like living on the edge, make sure to give 3.15 beta 1 a spin when it drops next week and [file any issues](https://github.com/python/cpython/issues) you find. One more thing: this newsletter takes real work to edit and curate. If you've got something Python core related to share, or just want to help out, please file [an issue on GitHub](https://github.com/savannahostrowski/coredispatch.xyz/issues) or reach out!
Core Dispatch #2
April 4 – 16, 2026
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](https://discuss.python.org/t/reverting-the-incremental-gc-in-python-3-14-and-3-15/107014) 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](https://discuss.python.org/t/moving-to-a-new-platforms-directory/105215/17), 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](https://github.com/python/cpython/issues) you find.
Core Dispatch #1
Mar 21 – Apr 4, 2026
Welcome to the very first edition of Core Dispatch! This is a new newsletter that will cover the latest news and updates from the Python core development community. Each issue will include a summary of recent releases, official news, PEP updates, steering council meetings, merged PRs, discussions, and upcoming events. If you have any feedback or suggestions for future issues, please [open an issue](https://github.com/savannahostrowski/coredispatch.xyz). If you're interested in joining the editorial team or contributing content, please let us know! Now, here's what's new: three CPython releases are slated to drop on Tuesday: 3.13.13, 3.14.4, and 3.15.0a8. PEP 803 got accepted, so free-threaded builds now have a stable ABI (extension authors, rejoice). Ken Jin also wrote up what's going on with the JIT in 3.15. Worth a read if you missed it. 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](https://github.com/python/cpython/issues) you find.
Never miss an edition
Delivered to your inbox.