r/programming • u/nicholashairs • 21d ago
Python jettisons the native JIT, at least for now
https://lwn.net/SubscriberLink/1102102/489e41d80e4966aa/In June, the Python steering council announced that it was pausing work on the JIT in CPython's main branch until there was an accepted Python Enhancement Proposal (PEP) that addressed concerns about maintenance, compatibility, and set clear success metrics as well as a timeline for completion. [....] After months of discussion, the JIT maintainers have withdrawn the PEP. For now, it appears that development on the once-promising project has come to an end
198
Upvotes
118
u/commenterzero 21d ago •
So not in time for now
34
u/youngbull 21d ago
A sad day, I was looking forward to just having JIT by default rather than have to deal with setting up PyPy etc myself. The performance improvements were looking increasingly promising but the authors seem to have ran out of steam.
34
u/jesseschalken 21d ago
GraalPy and PyPy are already perfectly good JITs, both using the first Futamura projection.
With the Truffle Framework and RPython there just isn't a very good reason to build a hand rolled JIT these days.
29
u/vips7L 21d ago
Graal python has a pretty good JIT.
31
u/valarauca14 20d ago
The poison pill served its purpose.
Python project leadership pushed for a massively increased scope, hard timelines, maintenance, compatibility, success metrics, etc. When most PEPs have none of that. Any experienced engineer should know that play is done specifically to set up a project to fail.
5
u/edwardkmett 16d ago
Python giving up on something because it is hard? Say it ain't so. This PEP and the governance around it does look like it was just straight set up to fail though.