TL;DR
The Python Steering Council has asked for a pause on all new features and optimizations for the experimental JIT in CPython. A formal PEP process will define its future support and stability. No timeline for resumption has been set.
The Python Steering Council has ordered a pause on all new development related to the experimental JIT compiler in CPython, pending the approval of a formal PEP that will define its long-term support and stability. This decision affects ongoing feature work and optimizations, emphasizing the need for a clear community process.
Over the past several years, core developers and contributors have been building a JIT compiler within the main branch of CPython. Despite encouraging performance improvements, the project has remained an experimental effort, with questions about maintenance, security, and compatibility remaining unresolved, as outlined in the informal PEP 744.
The Steering Council has now formally requested that no new JIT features, optimizations, or performance improvements be added until a dedicated Standards Track PEP is submitted and approved. Bugfixes and security patches may continue normally. This move aims to bring transparency and formal support to the project, which has undergone multiple re-architectures without a clear, community-backed plan.
Why It Matters
This development is significant because it halts potentially disruptive changes to a major component of CPython, the reference implementation of Python. It underscores the importance of formal processes in language development, especially for features that impact security, compatibility, and long-term maintenance. The decision also reflects a broader effort to ensure experimental features are properly vetted before becoming part of the main codebase.
Python JIT compiler development book
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background
The JIT project was initially merged into CPython as an experiment, with PEP 744 serving as an informational document outlining its design and open questions. Over time, multiple proposals and re-architectures have been attempted, but a comprehensive, community-approved plan for its support has yet to be established. The recent move aligns with previous community standards that experimental features should not be integrated into the main branch without formal backing.
“The Steering Council’s decision to pause new JIT development reflects the need for a formal, community-approved plan that clarifies its long-term role in CPython.”
— an anonymous researcher
“We want to give the project and community clarity and explicit commitments before moving forward with further development.”
— a member of the Python Steering Council
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 when a community-backed PEP will be submitted or approved, and whether the current architecture will be considered stable enough to support future development. The future of the JIT beyond the six-month window remains uncertain, and the community has not yet proposed alternative implementation strategies or timelines.
Python debugging and security tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What’s Next
The next step is for the community to draft and submit a Standards Track PEP outlining the JIT’s maintenance plan, guarantees, and compatibility considerations. The Steering Council will review and decide whether to accept or reject the proposal within approximately six months. If no PEP is approved within this period, the current JIT code will be removed from the main branch, and development will continue outside the core repository.
Python core development reference
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Why was the JIT project paused?
The pause was requested by the Python Steering Council to ensure that the JIT’s future is supported by a formal community process, including a PEP that clarifies its long-term maintenance, guarantees, and compatibility issues.
Does this mean the JIT will be removed from CPython?
Not immediately. The current instruction is to halt new development, but bugfixes and security patches may continue. If no PEP is approved within six months, the JIT code is expected to be removed from the main branch.
Can community members propose alternative solutions?
Yes. The Steering Council has invited proposals and alternative approaches to be discussed during the PEP process, which may include different implementation strategies or infrastructure designs.
What does this mean for Python users and developers?
It means that ongoing improvements to the JIT will be temporarily halted until a formal plan is approved, ensuring stability and clarity for downstream users, maintainers, and developers.
Source: Hacker News
