TL;DR
The Python Steering Council has requested a halt on all new development of the experimental JIT compiler in CPython until a formal process is completed. This move aims to evaluate long-term support, compatibility, and community consensus.
The Python Steering Council has formally requested a halt to all new features and optimizations for the experimental JIT compiler in CPython until a community-supported PEP is submitted and approved, marking a significant shift in the project’s development process.
Over the past several years, core developers and contributors have been working on integrating a JIT compiler into the main branch of CPython as an experimental feature. Despite notable performance improvements, the project has yet to undergo a formal review process or obtain community consensus for long-term support, security, and maintenance commitments.
In a recent announcement, the Steering Council emphasized that the JIT was initially introduced as an experiment via an informal proposal (PEP 744) that outlined open questions around guarantees, tooling, and downstream obligations. They clarified that no new features, optimizations, or performance work should be added to the main branch until a formal Standards Track PEP is submitted, discussed, and accepted. Bug fixes and security patches may continue as normal.
Why It Matters
This decision matters because it signals a shift towards greater procedural rigor in Python’s development, especially for large, experimental features like the JIT. It also highlights ongoing community concerns about sustainability, compatibility, and the future of the JIT within CPython, potentially affecting performance optimization efforts and third-party integrations.
Python 3.13.7 The Complete Guide: The Complete Developer's Guide to Modern Python 3.13, from Core Concepts to Advanced Concurrency and the new JIT Compiler
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background
The JIT project has been under development for several years, undergoing multiple architectural re-works. It was initially merged as an experimental feature with limited formal oversight, and a related PEP (PEP 744) provided only an informational outline rather than formal commitments. The recent move to pause development reflects the community’s desire for a structured review process before making the JIT a supported component of CPython.
“The Steering Council’s request for a formal PEP is about ensuring long-term support, security, and community consensus.”
— an anonymous researcher
“No new JIT features should land on main until a community-backed PEP is approved.”
— an anonymous researcher
Python Performance Engineering: Optimization Techniques Explained
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What Remains Unclear
It remains unclear how long the community review process will take, whether alternative proposals will be introduced, or if the current architecture of the JIT will be significantly revised. The future of the JIT as a supported feature is contingent on the outcome of the upcoming PEP process.
CPython Internals: Your Guide to the Python 3 Interpreter
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What’s Next
The Python community has six months to submit and resolve a formal PEP outlining the long-term plan for the JIT. If no such PEP is accepted within this window, the JIT code will be removed from the main branch, and development will continue outside the core repository.
Security Patch, 2 Pcs Reflective Security Hook and Loop Patch for Vest Printed Letters Embroidery Patches for Officer Guard Custom Uniforms Vest, Jacket, Carrier, Bag, Hat (Black, 1 Small and 1 Large)
【Package Content】The package contains two security patches for vest, one small (5.5 x 2.5 inches) and one large…
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Why has the Python Steering Council asked to pause JIT development?
The Council wants to ensure formal community consensus, long-term support, security, and compatibility before making the JIT a permanent part of CPython, which requires a structured review process.
Can ongoing bug fixes and security patches continue?
Yes, bug fixes and security updates may continue as normal, but no new features, optimizations, or performance work should be added until a PEP is approved.
What is the next step for the JIT project?
The community has six months to submit a Standards Track PEP. During this period, discussions will focus on defining maintenance plans, compatibility guarantees, and success metrics.
Will the JIT architecture change as a result of this decision?
It is not yet clear whether the current architecture will be revised or stabilized before the PEP process is complete; that depends on community feedback and proposals.
What happens if the PEP is not accepted within six months?
If no PEP is accepted, the JIT code will be removed from the main branch, and further development will occur outside of the core CPython repository.
Source: Hacker News
