[pjmlp]

So it will join PyPy and GraalPy in the corner.

Python JIT history is full of drama, and no, Smalltalk, Common Lisp, Interlisp-D, SELF are just as dynamic if not more.

[stevefan1999]

Honorable mention: https://github.com/tonybaloney/Pyjion

[ck45]

Not to forget Unladen Swallow Which even tried to merge into CPython: https://peps.python.org/pep-3146/

[scott_w]

JIT in CPython has nothing to do with PyPy or GraalPy: it's its own thing. If they can't get a PEP accepted within 6 months then it's best that the code isn't weighing on the main codebase until an approach can be agreed, at which point work integrating it into main can restart. It's not an all-or-nothing situation.

[pjmlp]

> JIT in CPython has nothing to do with PyPy or GraalPy: it's its own thing.

I haven't said otherwise.

[scott_w]

So why did you bring them up…

[pjmlp]

My words were

> So it will join PyPy and GraalPy in the corner.

If you cannot understand what that means, I am not a English professor.

[scott_w]

I understand your words, I don’t understand why you think they’re relevant to the discussion.

[pjmlp]

Relegated to niche users, just like the other two.

[onlyrealcuzzo]

And Ruby

[petre]

Ruby has not one, two, but three JITs.

[pjmlp]

Actually more, are you country JRuby, TruffleRuby and RubyMotion.

[throwaway81523]

CL is definitely less dynamic than Python. Dunno about the others.

[pjmlp]

Why do you think so?

All of them support changing anything at anytime, killing all JIT assumptions, and forcing it to redo the world.

Stop execution, land into the debugger, change whatever code you feel like during the debugging session and then redo last statement, continuing execution.

There are also ways to do this on fly, without necessarily using the debugger.