The Python Steering Council released a statement on the just‑in‑time (JIT) compiler in CPython’s main branch. After years of work by core developers, recent benchmarks show measurable speed gains, but the feature remains experimental. The council thanks contributors for their careful engineering and cites the informational PEP 744, which outlined criteria for graduating the JIT to a supported component.

Council members acknowledge the JIT’s multiple re‑architectures and the lack of formal commitments on maintenance, security review, debugging support, and downstream packaging, including a formal security audit and out‑of‑process tooling support. They now request a Standards Track PEP to define guarantees, maintenance plans, compatibility with profilers and other tooling. No new features or optimizations may land on main until such a PEP is accepted.

The council sets a six‑month window for submitting and resolving the required PEP; failure to approve it will trigger removal of the JIT code from CPython’s repository. This deadline forces the community to decide whether the JIT becomes a permanent, well‑defined subsystem or moves to an external project, clarifying CPython’s runtime evolution and any associated licensing considerations.