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 #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.
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](https://github.com/python/devguide/pull/1804) in the [Devguide](https://devguide.python.org/), 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](https://github.com/python/release-tools/pull/394). Looking ahead, the [EuroPython 2026 Language Summit](https://ep2026.europython.eu/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](https://vstinner.github.io/free-threading-reference-counting.html) 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](https://github.com/python/cpython/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](https://github.com/python/cpython/issues) you find.