Python's Experimental JIT To Be Removed
AIThis post was created with the assistance of artificial intelligence (AI).

TL;DR

The maintainers of CPython’s experimental just-in-time compiler have withdrawn PEP 836, the proposal created after Python’s steering council asked for a clearer case for continuing JIT development. The council had said the proposal was too vague on support plans and performance criteria; the supplied report says the JIT is now on its way out, but does not specify a removal date or the exact next steps.

CPython’s experimental just-in-time compiler is facing removal after its maintainers withdrew PEP 836, a proposal intended to address concerns raised by Python’s steering council. The council had asked for a plan covering maintenance, compatibility, performance goals and a timeline; after reviewing the proposal, it said those issues were not addressed specifically enough. The available report says JIT development appears to have come to an end, but does not give a removal date or describe a final decision to delete the code.

Before you orderOffer from Amazon

Get the latest gadgets delivered free with Prime

  • Fast, free delivery on millions of items
  • Prime Video, Amazon Music and more included
  • Member-only deals all year
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

The JIT was added to CPython by Brandt Bucher in early 2024 and included with the Python 3.13 release. Its development had proceeded under PEP 744, an informational document that described the work but did not constitute formal approval of the JIT as a supported CPython feature. In June, the steering council asked the maintainers to produce a standards-track PEP addressing the project’s long-term commitments and success measures.

Bucher, Savannah Ostrowski and Ken Jin published PEP 836 on July 3 for community feedback. Following months of discussion, the JIT maintainers withdrew it. The steering council’s September 21 statement said PEP 836 answered the questions in its request, though some answers were less convincing than others. It said the document was not specific enough about support plans and performance criteria, and was too vague or optimistic on other points.

The council said its immediate decision was about whether the JIT should continue as an experiment in CPython’s main branch—not whether the compiler should become a supported feature. It had set a six-month deadline for a PEP to be submitted and accepted, warning that otherwise it would require the JIT code to be removed from the main branch. The source report does not state whether that deadline has expired, whether another proposal is planned, or when removal would occur.

At a glance
updateWhen: Developing; the steering council statem…
The developmentThe maintainers withdrew the PEP intended to address the steering council’s concerns about CPython’s experimental JIT, leaving its continued development in doubt.

What JIT Removal Could Mean

Removing the code would end the JIT’s place as an ongoing experiment in CPython’s main development branch, rather than simply changing a user-facing setting. The council’s concerns reflect the work needed to maintain a compiler alongside the rest of Python: developers and downstream distributors need to understand the support commitment, compatibility implications and criteria by which its performance would be judged.

The debate also touches other work in the Python ecosystem. The council cited efforts to make the JIT work with instrumentation, debugging and profiling, as well as external and JIT-adjacent projects such as CinderX, Numba and PyTorch’s compile features. Without a clear scope and maintenance plan, continued experimentation could affect other development priorities and leave core developers, package maintainers and users uncertain about changing behavior and APIs.

For Python users, the immediate significance is limited by the lack of a stated removal schedule or details about any release impact. The development does not establish that Python’s broader performance work is ending, nor does it say that external JIT projects will stop. It signals that the CPython JIT’s future depends on a proposal and commitments acceptable to the steering council.

Products Worth Considering

Apple MacBook Air 15-inch Laptop with M5 Chip, 24GB Memory, 1TB SSD, Midnight

Apple MacBook Air 15-inch Laptop with M5 Chip, 24GB Memory, 1TB SSD, Midnight

Sonos One Two-Room Set Smart Speakers with Built-In Alexa, Black

Sonos One Two-Room Set Smart Speakers with Built-In Alexa, Black

As an affiliate, we earn on qualifying purchases.

How the JIT Reached This Point

A major CPython feature would generally be expected to proceed through a standards-track Python Enhancement Proposal. Bucher announced his intent to merge the JIT after presenting the work at a core developer sprint, but had not submitted such a proposal. After prompting from steering council member Thomas Wouters, Bucher and Ostrowski drafted PEP 744, which documented the JIT without seeking formal consensus to proceed.

The council’s June request followed discussion about how the JIT fit alongside other work. Wouters said there was no single event that triggered the request; the council wanted to avoid the JIT interfering with other projects and waited until after the Python 3.15 beta release to make clear that it was comfortable with the status quo for that release. It asked for a case for the JIT as a supported, non-experimental part of CPython, including guarantees, maintenance commitments and effects on redistributors.

PEP 836 drew both favorable and critical feedback. One recurring objection was that it combined the case for accepting the JIT with implementation details. Mark Shannon argued that the proposal should focus on acceptance goals and leave implementation details out. Ostrowski defended the document’s approach, saying goals without an accompanying plan would be difficult to assess. The council later said it was judging whether the JIT should remain an experiment in the main branch, not deciding whether it met the bar for permanent support.

“The PEP did answer all of the questions highlighted in the council’s request, although perhaps some less convincingly than others.”

— Python steering council, in its September 21 statement

Removal Timing Remains Unspecified

The supplied report does not specify when the JIT code will be removed, whether the steering council has issued a final removal order, or whether a replacement PEP is being prepared. Although the council set a six-month deadline for an accepted proposal and said removal would be required if that condition was not met, the material provided does not establish the deadline’s status or the date from which it should be counted.

It is also unclear what removal would mean for specific Python releases, for users who have tested the experimental compiler, or for related performance projects. The council’s statement describes concerns about support plans, performance criteria and uncertainty for developers and users, but the available account does not reproduce the complete ten-point list it requested the PEP to address. The maintainers’ withdrawal is confirmed in the report; the precise technical and release consequences are not.

Council Decision and Code Changes

The next developments to watch are a formal steering council decision on the JIT’s status and any resulting changes to CPython’s main branch. If the council applies the removal condition it described, the JIT code would be deleted from that branch; the source material does not give a schedule for such work.

A renewed proposal could also clarify whether the maintainers intend to continue the project under revised commitments, but no replacement PEP or plan is identified in the supplied report. Until the council or maintainers publish further details, the confirmed position is that PEP 836 has been withdrawn and the JIT’s future in CPython remains unresolved.

Key Questions

What happened to Python’s experimental JIT?

The JIT maintainers withdrew PEP 836, the proposal drafted after the steering council asked for a clearer plan for the compiler. The report says development appears to have ended, while the exact removal decision and schedule remain unspecified.

Why did the steering council raise concerns?

The council said PEP 836 was not specific enough about support plans and performance criteria, and was vague or overly optimistic in other areas. It also wanted clarity about maintenance, compatibility, timelines and effects on redistributors.

Is the JIT already removed from CPython?

The source material says the JIT is on its way out, but it does not give a removal date or confirm that the code has already been deleted. The council had said removal would be required if an accepted PEP was not produced within its six-month deadline.

Does this end performance work in Python?

No such conclusion is supported by the report. The dispute concerns the experimental JIT in CPython’s main branch; the council also referred to external and JIT-adjacent work, including CinderX, Numba and PyTorch’s compile features.

Could another proposal keep the JIT alive?

That remains possible, but the supplied report identifies no replacement PEP or new schedule. Any next step would depend on further action by the maintainers and the steering council.

Source: hn

You May Also Like

Steel Bank Common Lisp Version 2.6.7

Steel Bank Common Lisp version 2.6.7 has been officially released, introducing performance improvements and bug fixes for the popular Lisp implementation.

Ghostel.el: Terminal emulator powered by libghostty

Ghostel.el introduces a new terminal emulator built on libghostty, offering enhanced performance and compatibility for developers.

SVG Carving Animation: A Look Inside “The Runestone Field — Carve Words Into Winter” (FABLE/175)

A detailed look at how SVG carving animation brings ‘The Runestone Field’ to life, blending history and technology for immersive storytelling.

Logistics Workspace For Citizens’ Assembly Organizers

A new logistics workspace prototype is being tested to streamline planning for civic dialogue forums, aiming to improve efficiency for nonprofits.