Python's experimental JIT to be removed
- ID
- 40076
- Status
- summarized
- Published
- 27 Oct 2026, 7:17 PM
- Fetched
- 28 Oct 2026, 1:56 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://lwn.net/SubscriberLink/1102102/0c00e4d550f25f8c/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 6.5
- Created
- 28 Oct 2026, 1:57 AM
- Tags
- Audience
- developersvibe_codersai_ml_learners
What happened
CPython's experimental JIT, added in 2024 for Python 3.13, is being removed after the Python steering council paused JIT work in June and the maintainers withdrew PEP 836 following months of discussion. The JIT originally landed via Brandt Bucher without a standards-track PEP, and was proceeding under informational PEP 744 until the council asked for a new PEP covering maintenance, compatibility, success metrics, and timeline.
Why it matters
If you were benchmarking or planning around CPython's experimental JIT for Python 3.13+ speedups, do not assume it will remain or become a supported performance path. Treat this as a signal to keep performance-sensitive Python work on established options and to watch how CPython handles major runtime changes without a standards-track PEP.
Discussion angle
Should CPython prioritize a supported JIT, or is the maintenance and compatibility burden too high? The withdrawal of PEP 836 makes that governance-versus-performance tradeoff concrete.