TL;DR
The Python Steering Council has asked for a halt on new features and optimizations for the CPython JIT compiler. A formal PEP will be drafted within six months to define its future, affecting ongoing performance work and community contributions.
The Python Steering Council has officially requested a pause on all new development related to the experimental JIT compiler in CPython until a formal proposal is adopted, marking a significant shift in the project’s direction.
Over several years, core developers have been building a JIT compiler within CPython, aiming to improve performance. Despite encouraging results, the project has undergone multiple re-architectures, and its experimental status remains unformalized.
The Steering Council clarified that no new features, optimizations, or performance enhancements should be added to the main branch until a dedicated Standards Track PEP is approved. Bug fixes and security patches will continue as usual.
The decision stems from concerns over the lack of a formal process to define the JIT’s long-term maintenance, compatibility guarantees, and its impact on existing tooling. The council emphasized that the JIT was initially an experimental effort, with its status needing formalization through a community-approved PEP.
Why It Matters
This development marks a critical pause in the ongoing efforts to integrate a JIT compiler into CPython, the reference implementation of Python. It underscores the importance of formal processes for experimental features, especially those with potential widespread impact on performance and ecosystem compatibility. The move aims to bring clarity, stability, and community consensus before further development continues, affecting current and future performance projects.
Python JIT compiler performance tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background
The JIT project was introduced as an experimental feature, with its initial design documented in PEP 744, which remains informational. Despite several improvements, questions about long-term support, security, debugging, and compatibility have persisted. The project has seen multiple re-architectures, reflecting the complexity of integrating a high-performance compiler into the core language.
Historically, experimental features in CPython have required formal PEPs before substantial development, but the JIT was merged into main as an experiment without a formal process, leading to concerns about its future stability and maintenance.
“The Steering Council’s decision to pause new JIT development reflects the need for a clear, community-backed plan to ensure sustainability and compatibility.”
— an anonymous researcher
“We want to give the project and the community the clarity and explicit commitments that a change of this magnitude deserves.”
— a member of the Python Steering Council
Python debugging and profiling tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What Remains Unclear
It is not yet clear what specific alternative proposals might be introduced or how long the formal process will take. The exact timeline for the PEP’s approval and the future of the current JIT code remains uncertain. Additionally, the impact on ongoing performance improvements and community contributions is still developing.
Python development environment setup
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 Standards Track PEP that addresses the JIT’s long-term support, maintenance, and integration. If no PEP is accepted within this window, the JIT code will be removed from the main branch, and development will continue outside the core Python repository.
Python performance optimization books
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 Steering Council requested a formal PEP to define the JIT’s long-term support, stability, and integration before further development. This pause aims to ensure community consensus and proper governance.
Will existing JIT features continue to work?
Yes, bug fixes and security patches will continue. However, no new features or optimizations are allowed until the PEP process concludes.
What is a PEP, and why is it important?
A PEP (Python Enhancement Proposal) is a formal document that describes a new feature or process. It ensures community discussion, consensus, and proper governance before significant changes are made.
Could the JIT project be permanently discontinued?
If no PEP is accepted within six months, the current JIT code will be removed from the main branch, and development will shift outside the core repository. The future of the project depends on community approval of the PEP.
Source: Hacker News
