A Pause for the Python JIT
a day ago
- Python 3.13 added an experimental just-in-time (JIT) compiler to optimize CPython execution.
- The Python steering council paused new JIT development in the main branch until a standards-track PEP is accepted.
- PEP 744 was an informational PEP that allowed JIT work to proceed without formal consensus.
- PEP 836 ('JIT Go Brrr') was created to propose the JIT as a supported part of CPython, with a 2.5-year timeline and milestones.
- The council requested the PEP address long-term maintenance, compatibility with CPython features and third-party JITs, stability, and clear metrics.
- Discussion emerged about splitting PEP 836 into two separate PEPs: one for acceptance criteria and one for implementation plans.
- Development of the JIT is currently on hold; no direct opposition exists, but debate continues on requirements and details.