Editions
Every edition of Core Dispatch.
Core Dispatch #11
Aug 27 – Oct 9, 2026
Welcome back to Core Dispatch! This edition covers August 27 through October 9, 2026 (It's been a while 😅). Python 3.15.0 final landed today after an extra release candidate for lazy-import blockers. Huge congrats to Hugo van Kemenade for getting the 3.14 and 3.15 feature releases out the door! The latest maintenance releases also mark Python 3.10's end of life and 3.13's move to security-only support. Python 3.16.0 alpha 1 is expected on October 13. New PEPs revisit None-aware access, coalescing operators, incremental garbage collection, and more expressive type annotations. PEP 755 was withdrawn; PyPI's namespace rules will instead live in PyPI policy. On CPython's main branch, notable merges improve free-threaded performance and fix security and memory-safety issues. The Python Language Summit writeups cover free-threading, garbage collection, the buffer protocol, and Rust in CPython. The PSF Board and inaugural Python Packaging Council election results are out, and Nathan Goldbaum and Sergey Miryanov have joined the core team. Please test your projects with Python 3.15.0 and publish compatible wheels where applicable. If you find a bug, file a CPython issue.
Core Dispatch #10
August 5 – 27, 2026
Welcome back to Core Dispatch! This edition covers August 5 through August 27, 2026. Python 3.12.14, 3.11.16, and 3.10.21 shipped on August 12. Next up is Python 3.15.0 release candidate 2, due September 1. There are five new PEPs to catch up on. PEP 805 proposes a model for safe parallel Python. PEP 843 and PEP 844 offer two approaches to explicit module exports. PEP 841 proposes syntax for frozen types, while PEP 839 adds C APIs for building immutable collections. PEP 833 also reached Final, freezing the HTML form of the simple repository API. HTML support stays, but future standards work moves to JSON. Speaking of PEPs, PEP 11 was also updated to list RISC-V as a tier 3 platform. Many core team members spoke about Python core development at EuroPython this year. All nine talks are in this edition's Core Team Musings, covering the CPython ABI, the JIT, free-threading, interpreter internals, security, and contributing to Python. Voters can also catch up on nominee AMAs for the PSF Board and inaugural Python Packaging Council elections before ballots open on September 1. Python 3.15 is in the release candidate phase, so this is the moment for maintainers to test their projects and publish Python 3.15 wheels to PyPI. Wheels built against the 3.15 release candidates will work with future 3.15 releases, and publishing them now helps downstream projects test too. Please file any CPython issues you find.
Core Dispatch #9
Jul 18 – Aug 5, 2026
Welcome back to Core Dispatch! This edition covers July 18 through August 5, 2026. Python 3.15.0 release candidate 1 landed on August 4, followed by Python 3.14.7 and 3.13.15 on August 5. With the first release candidate here, 3.15 is firmly in the home stretch. Two new PEPs joined the queue this fortnight. PEP 842 proposes explicit module exports, while PEP 837 explores an extensible protocol for JSON serialization. There is also lively pre-PEP discussion around PEP 841, which proposes frozen syntax for immutable types. PEP 828 has also been accepted by its PEP delegate, clearing the way for yield from in asynchronous generators. Elsewhere, PyPI announced that releases will stop accepting new files after 14 days, nominations for the inaugural Python Packaging Council are about to open, and core developer Petr Viktorin was named a PSF Fellow. If you missed EuroPython, this edition's Core Team Musings includes the new CPython and Steering Council panel recordings, along with the video edition of a very fun, live core.py interview with Guido van Rossum. Python 3.15 has now entered the release candidate phase, so this is the moment for maintainers to test their projects and publish Python 3.15 wheels to PyPI. Wheels built against the 3.15 release candidates will work with future 3.15 releases, and publishing them now helps downstream projects test too. Please file any CPython issues you find.
Core Dispatch #8
July 5 – 18, 2026
Welcome back to Core Dispatch! This edition covers July 5 through July 18, 2026. Python 3.15.0 beta 4 landed today, July 18 (we just released it at the EuroPython sprints!), with 3.13.15, 3.14.7 and the first 3.15 release candidate following on August 4. It's EuroPython week! Much of the core team has been gathered in one place for our annual Language Summit (blog posts to come!) and the conference. Recordings aren't up just yet, but as promised with the PyCon US talks, once they are, we'll pull talks and Language Summit coverage from the team into a future edition. On the PEP front, discussion is lively: PEP 835 (shorthand syntax for Annotated metadata) and PEP 836 ("JIT Go Brrr") are both drawing dozens of new replies, and a few fresh PEPs — including PEP 840 on name resolution in class namespaces — have joined the queue. Don't miss the "One More Thing" at the bottom of this edition. This one's a little sillier (correction: more unhinged) than usual, but we think you'll enjoy it. As always, if you maintain a package or just like living on the edge, give the final 3.15 beta a spin and file any issues you find.
Core Dispatch #7
Jun 19 – Jul 5, 2026
Welcome back to Core Dispatch! This edition covers June 19 through July 5, 2026. Python 3.15.0 beta 3 landed on June 23, and beta 4 is up next on July 18, with 3.13.15 and 3.14.7 following on August 4. Last edition, we covered the Steering Council's request that the experimental JIT chart its future through a Standards Track PEP. A new PEP has now been drafted and discussion has started: PEP 836, "JIT Go Brrr: The Path to a Supported JIT Compiler for CPython," sketches what moving the JIT from experiment to supported feature could involve, from performance expectations to interop and tooling compatibility. PyCon US 2026 talk recordings have also started landing, and we've pulled a few from the core team into Core Team Musings below: Pablo Galindo Salgado and László Kiss Kollár on Python 3.15's new Tachyon sampling profiler, Thomas Wouters on the past, present, and future of free-threaded Python, and Emma Smith on Rust for CPython. Not everything is up yet, so expect more picks as the rest are published. On the packaging side, the inaugural Packaging Council election dates are out. And looking ahead, EuroPython 2026 kicks off July 13, so expect a wave of talks and Language Summit coverage to pull from in a future edition. As always, if you maintain a package or just like living on the edge, give the latest 3.15 beta a spin and file any issues you find.
Core Dispatch #6
June 4 – 19, 2026
Welcome back to Core Dispatch! This edition covers June 4 through 19, 2026. Python 3.14.6 and 3.13.14 landed on June 10, and the next milestone is 3.15.0 beta 3 on June 23. The big news this fortnight comes from the Steering Council, who put out an announcement on the path forward for the experimental JIT. The JIT entered CPython's main branch as an experiment, alongside the Informational PEP 744. The Council would like to see its path forward worked out through a Standards Track PEP, giving the project the explicit, structured conversation it hasn't really had yet about what people expect from a JIT, including performance targets, interop guarantees, and tooling compatibility. On a related note, JIT contributors have opened a thread to gather community perspectives on the JIT as they begin drafting that PEP. Give it a read, and if you've got experiences, expectations, or concerns to share, it's a good place to weigh in. It's been a bit quieter on the PEP front over the past two weeks, though PEP 835, a shorthand syntax for Annotated type metadata, was newly drafted. Over on the PSF side, the Board has published the draft of its 2026 strategic plan: six organizational goals and four program goals spanning financial sustainability, supply chain security, and community empowerment. The feedback window is open through June 25, so if you've got thoughts, now's the time. The 2026 PSF Board election dates are out too. As always, if you maintain a package or just like living on the edge, give the latest 3.15 beta a spin and file any issues you find.
Core Dispatch #5
May 18 – Jun 4, 2026
Welcome back to Core Dispatch! This edition covers May 18 through June 4, 2026. As promised, Python 3.15.0 beta 2 landed on June 2. Two more milestones are close behind: 3.13.14 and 3.14.6 on June 9, followed by 3.15.0 beta 3 on June 23. There's also a healthy batch of changes landing for 3.15: an O(n^2) blowup in unicodedata.normalize() was fixed, the XML parser gained support for multi-byte encodings, and a round of deprecation warnings went in for the ast module and abc's abstractclassmethod/abstractstaticmethod/abstractproperty. On the project side, the Python Security Response Team (PSRT) landed an initial Python security policy in the Devguide, giving the vulnerability reporting and response process a documented home. And dev builds of 3.15+ now report a version like 3.15.0b2+dev instead of the old bare-plus 3.15.0b2+, which wasn't PEP 440-compliant. Looking ahead, the EuroPython 2026 Language Summit topics are out, with a lineup spanning a Rust-for-CPython roadmap, the future of free-threading, garbage collection, and the buffer protocol. If you're interested in CPython internals, Victor Stinner has a great writeup on free threading internals and reference counting that's well worth your time. As always, if you maintain a package or just like living on the edge, give the latest 3.15 beta a spin and file any issues you find.
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 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 we mentioned last edition. The Steering Council was busy. PEP 661 was accepted after nearly five years of discussion. PEP 788, PEP 820, PEP 829, and PEP 831 also got the green light, while PEP 708 and PEP 806 were turned down. Big fortnight on the PEP front! It's also a great time to review the 3.15 What's New 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 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 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 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.
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. 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 you find.
Never miss an edition
Delivered to your inbox.