PEP 836: JIT Go Brrr: The Path to a Supported JIT Compiler for CPython

[brettcannon]

@timkofu

We Python users are very much looking forward to having the best possible JIT that works with free threading.

We want to extract the most possible work from the hardware we can afford, and a JIT would help with that.

Then hopefully you and others can organize yourselves to continue on with the work outside of the CPython repo.

@barry-scott

Does this mean that the JIT work is stopped?

In CPython’s repo, yes. Whether others in the community organize to keep it going is up to the community.

@Sacul

My worry is the 6 months window for the JIT to be kept in Main

The point of the PEP was to justify the JIT work staying in main, so the withdrawal of the PEP means it will come out and live somewhere else (“We’ll make the reference implementation available and link it from the withdrawn PEP so others who are interested can explore and build on that.”).

[duncathan (Dunc Graham)]

@brettcannon

The point of the PEP was to justify the JIT work staying in main, so the withdrawal of the PEP means it will come out and live somewhere else

Well, strictly speaking, there is still a window for an alternative PEP to be submitted and discussed (until December 5th, I believe?) according to the timeline laid out by the SC. Of course that’s a very narrow window in PEP timescales, but the possibility does exist until then, no?

[brettcannon]

@duncathan

Well, strictly speaking, there is still a window for an alternative PEP to be submitted and discussed (until December 5th, I believe?) according to the timeline laid out by the SC. Of course that’s a very narrow window in PEP timescales, but the possibility does exist until then, no?

Not really as all the people actively driving the JIT were either authors on that PEP or contributors to it. Plus this decision was made at the core dev sprints where most of the people working on the JIT currently are, so they would have made the decision as a group (otherwise the PEP would have just been handed over to someone else to continue working on it).

[h-vetinari]

@brettcannon

Plus this decision was made at the core dev sprints where most of the people working on the JIT currently are

Would be nice to have an insight into what were the deciding factors for the decision to abandon this effort (at least in its current form). Perhaps someone who was involved would have time to write something up after the core dev sprints…?

[eendebakpt (Pieter Eendebak)]

@savannahostrowski @kj0 @brandtbucher and others contributing. Thanks for the time and effort you put into the PEP!

Even though this one is withdrawn for now, I think the PEP is a good basis for either a follow-up, or an informed decision to go in another direction.

[timkofu (Timothy Makobu)]

Then hopefully you and others can organize yourselves to continue on with the work outside of the CPython repo.

There’s already [CinderX]( GitHub - facebookincubator/cinderx: High-performance Python runtime extensions · GitHub ) which works well, but isn’t part of Python core, requires catch up with releases; devs may not have it in mind as they improve and enhance Python, so time and effort will be spent getting new releases to work with it.

Would be nice to have an insight into what were the deciding factors for the decision to abandon this effort

Yes. It’s something many of us see as the last missing piece, and are looking forward to finally having it.