Python Language Summit 2026: what was decided and what was discussed

# At a glance July 14, 2026, at EuroPython in Kraków, Poland. Forty-seven Python core developers and invited guests attended. The meeting covered implementation-level changes and language design work that affect CPython, toolchains, and the contributor roadmap.

# Why this Summit matters

# Topics covered Talks addressed a mix of language design, runtime implementation, tooling, and community process. Key topic areas included:

• Concurrency and free-threading
• Rust integration and Rust-for-CPython efforts
• Garbage collection strategies (generational, incremental, or both)
• Memory APIs and tooling (memory buffer protocol, memory snapshots)
• Type-system work (PEP 827: Type Manipulation)
• Platform-specific support (macOS and Python)
• Namespacing and module layout
• Developer-in-Residence status and future priorities

# Notable talks and lightning sessions The Summit program listed these talks and presenters:

• "One namespace to namespace them all" by Pablo Galindo Salgado
• "macOS and Python" by Ned Deily
• "Garbage Collection: Generational? Incremental? Both!" by Mark Shannon
• "Memory Buffer Protocol" by Nathan Goldbaum
• "Memory Snapshots for CPython" by Hood Chatham
• "Rust for CPython" by David Hewitt
• "Spicycrab" by Kushal Das
• "Developer-in-Residence Update & Future" by Petr Viktorin
• "Free-Threaded Python Post-Era" by Donghee Na, Tobias Wrigstad, and Fridtjof Stoldt
• "PEP 827: Type Manipulation" by Michael J. Sullivan

• "One-time ABI breakage" by Mark Shannon
• "Safer and Generic Interruptions" by Daniele Parmeggiani
• "EktuPy, Scratch but Python" by Kushal Das
• "AGENTS.md for CPython" by Gregory P. Smith and Łukasz Langa
• "Please read PEP 836 (JIT go brrr)" by Ken Jin (listed with a question mark in the program)

# Procedural and compatibility notes The Summit highlighted compatibility and ABI topics. One lightning talk specifically addressed a potential one-time Stable ABI break to free previously reserved bits in PyObject headers. The writeups note trade-offs such a break would impose on third-party packages and how the evolution of free-threading and new ABI variants (abi3t) factor into the discussion.

# Community and next steps Morehouse, Hugo van Kemenade, Lysandros Nikolaou, and Łukasz Langa. Blog post summaries and separate deep-dives on several talks were published after the event. The alternating schedule between PyCon US and EuroPython means similar cross-Atlantic gatherings will recur yearly, giving maintainers an established cadence for face-to-face language-design work.

# How to follow up Read the published Summit blog posts and the linked deep-dive writeups for each talk to get implementation details and next steps. Several items (free-threading, garbage collection strategy, Rust integration, and ABI policy) will require follow-up discussions and design proposals in the CPython development process.