Core Dispatch
A regular digest of what's happening in Python core development — from merged PRs and PEP decisions to community discussions and upcoming events.
Recent Editions
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](https://peps.python.org/pep-0842/) proposes explicit module exports, while [PEP 837](https://peps.python.org/pep-0837/) explores an extensible protocol for JSON serialization. There is also lively [pre-PEP discussion around PEP 841](https://discuss.python.org/t/pep-841-adding-frozen-syntax-to-make-immutable-types-optimizable/108219), which proposes `frozen` syntax for immutable types. [PEP 828](https://peps.python.org/pep-0828/) 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](https://discuss.python.org/t/python-3-15-0-release-candidate-1-is-here/108395#p-298000-call-to-action-1). 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](https://github.com/python/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](https://peps.python.org/pep-0835/) (shorthand syntax for `Annotated` metadata) and [PEP 836](https://peps.python.org/pep-0836/) ("JIT Go Brrr") are both drawing dozens of new replies, and a few fresh PEPs — including [PEP 840](https://peps.python.org/pep-0840/) 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](https://github.com/python/cpython/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](https://peps.python.org/pep-0836/), "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](https://youtu.be/f1x4X83CDSA), Thomas Wouters on the [past, present, and future of free-threaded Python](https://youtu.be/PZu6LyiZVbM), and Emma Smith on [Rust for CPython](https://youtu.be/42kibVnUHYE). Not everything is up yet, so expect more picks as the rest are published. On the packaging side, the inaugural [Packaging Council election dates](https://blog.python.org/2026/06/2026-packaging-council-election-dates/) are out. And looking ahead, [EuroPython 2026](https://ep2026.europython.eu/) 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](https://github.com/python/cpython/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](https://discuss.python.org/t/an-announcement-from-the-steering-council-regarding-the-jit-project/107638). The JIT entered CPython's `main` branch as an experiment, alongside the Informational [PEP 744](https://peps.python.org/pep-0744/). 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](https://discuss.python.org/t/community-perspectives-on-the-jit-experiences-expectations-and-concerns/107737) 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](https://peps.python.org/pep-0835/), 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](https://pyfound.blogspot.com/2026/06/psf-strategic-plan-2026-draft-open-for.html): 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](https://pyfound.blogspot.com/2026/06/psf-board-election-dates-for-2026.html) 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](https://github.com/python/cpython/issues) you find.