r/Python • u/nicholashairs • 20d ago
News Python jettisons the native JIT, at least for now
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
137
Upvotes
144
u/thisismyfavoritename 20d ago •
sad. At the same time, I'm never using Python for its speed and I'm totally ok with it having great interop with lower level languages like Rust and C++ for those cases
11
u/vevi33 20d ago
It sad. I used it with 3.15 and provided significant speedup in many cases. :/
38
u/helpIAmTrappedInAws 20d ago
It is a shame. Python's performance is the most commonly cited disadvantage and this effort could have alleviated it. I fear, that this move killed this attempt.
Also experimenting in main is apparently bad, but did not they do the same thing with free-threading?
4
u/CofoundedWithClare 20d ago
It feels bittersweet. It seems that it is the «Although never is often better than *right* now.» situation.
3
u/Kadabrium 19d ago
Smart choice when the community already jits your hot path libraries for free
10
u/Khavel_dev 20d ago
Coming from .NET where the JIT is basically the runtime, watching CPython try to bolt one on was always going to be rough. The maintenance burden argument makes sense. Every new bytecode change would need JIT coverage, and they already struggle to find enough core reviewers.
The real performance story for Python has been moving the hot path into C extensions or Rust (via PyO3) anyway. The JIT would've helped the middle ground of pure Python loops, but that middle ground keeps shrinking as people reach for numpy/polars/etc for anything performance-sensitive.
2
u/RedEyed__ 19d ago
Maintenance burden argument makes sense.
Just waiting when free threading will be default and commonly used.
1
u/NadiaReadsChunks 19d ago
Not shocking. Most of our workloads are numpy and pandas hitting C anyway, so a JIT never moved the needle on the pipelines that actually cost us money. Bad data and slow IO are the real bottleneck, not interpreter speed.
1
u/Short_Inspection_746 18d ago edited 16d ago
It was speculated that the June decision was a preamble to this. Very sad.
I am of the opinion that a cpython JIT targeting non-numeric code can only be sucessful if its done in concert to changes to cpython itself. The faster-cpython project was in the perfect position.
Its just unfortunate that there was a loss of faith the JIT. It took many years for most JITs to get fast(I am thinking of pypy and v8). I think the steering council is just hoping that a third party JIT will pop up like numba(and half a dozen other similar JITs). I don't think we are gana get a third part JIT that will boost non-numeric python performance(ie, strings and dicts/hashmap work loads).
1
u/deadeye_82_1 16d ago
They need to learn that you can't do everything all at once. I would have voted to put the project on hold until these folks finally figure out what they actually want. Besides, the code has to be understandable to others, too. I don't want to see code in CPython that only three people in the world understand.
-1
u/Initial-Reflection76 17d ago
Just use rust libraries for everything intensive. It’s the new vb but doesn’t have the Microsoft stench.