TL;DR
The Python Steering Council has asked for a pause on new features and optimizations for the JIT compiler in CPython. This follows concerns about process adherence and long-term maintenance, pending a community-backed PEP. Bugfixes will continue as normal.
The Python Steering Council has formally asked developers to pause all new development on the experimental JIT compiler in CPython until a community-supported PEP is accepted, marking a significant step in managing the project’s future.
The JIT compiler, integrated into CPython as an experimental feature, has seen ongoing development over several years, with notable performance improvements. However, the Steering Council states that the project’s long-term stability and maintenance have not been sufficiently formalized through a PEP (Python Enhancement Proposal). As a result, they are requesting that no new features, optimizations, or performance work land on the main branch until a dedicated PEP is submitted and approved. Bugfixes and security patches may continue as usual. The decision follows concerns about adherence to formal processes and the need for clear guarantees regarding maintenance, compatibility, and community involvement. The Council emphasizes that this move is not a shutdown but a step toward establishing a sustainable, community-backed foundation for the JIT’s future in CPython.
Why It Matters
This development is significant because it halts ongoing experimental work that could impact Python’s core performance and ecosystem. It underscores the importance of formal processes for major features, especially those affecting the runtime environment. For developers and users, this means a temporary pause on new JIT features while the community works toward a transparent, well-defined plan for its future. The outcome could influence how experimental features are integrated into Python moving forward, emphasizing sustainability and community consensus.
Advanced Python 3.14.2 Internals and New Features: Mastering the Free-Threaded Interpreter, JIT Compiler Options, and Lazy Annotation Evaluation for Scalable Systems.
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background
The JIT compiler effort in CPython has been an ongoing, collaborative experiment involving multiple core developers. It was initially merged as an experimental feature via PEP 744, which was informational and left open questions about long-term support, security, tooling, and compatibility. Over the years, various proposals and architectures have been tested, but no formal process has yet been completed to make the JIT a supported, non-experimental feature. The recent decision reflects a recognition that the project needs a formal PEP to clarify its scope, maintenance, and guarantees before further development can proceed.
“The Steering Council’s request to pause new JIT development is about ensuring long-term stability and formalizing community support.”
— an anonymous researcher
“Bugfixes and security updates will continue, but no new features or optimizations are allowed until a PEP is accepted.”
— an anonymous researcher
High Performance Python: Practical Performant Programming for Humans
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What Remains Unclear
It is still unclear how long the community will take to draft and approve the PEP, or what alternative proposals might emerge. The exact timeline for resuming development depends on the PEP process and community consensus.
An Introduction to Using, Configuring and Customising Virtual Environments in Python
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 a formal PEP outlining the future of the JIT. During this period, developers are encouraged to propose alternative approaches or improvements within the framework of the PEP process. If no PEP is accepted by then, the JIT code will be removed from the main branch, and further development will continue outside the core Python repository.
Debugging Python Errors Faster: A practical guide to fixing bugs, reading tracebacks, and handling exceptions with confidence (Python to AI Fast Series)
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Why is the JIT being paused now?
The pause is to ensure that the JIT’s development follows a formal, community-approved process, addressing concerns about long-term maintenance, security, and compatibility guarantees.
Will existing JIT features continue to work?
Yes, bugfixes and security patches will continue as normal, but no new features or optimizations will be added until a PEP is approved.
How long will the pause last?
The community has six months to submit and resolve a PEP. If none is accepted by then, the JIT code will be removed from the main branch.
Can alternative proposals be considered?
Yes, the Steering Council encourages community proposals and discussions during the PEP drafting process.
What is the significance of this decision for Python’s future?
This move emphasizes the importance of formal processes for major features and aims to establish a sustainable, community-supported foundation for the JIT in CPython.
Source: Hacker News
