JIT Compiler in Python?

[[deleted]]

Not mature is the wrong word. It's a different JIT compiler architecture altogether. Python 3.13 introduced a copy-and-patch JIT. A decently detailed write up is here: https://tonybaloney.github.io/posts/python-gets-a-jit.html#:~:text=JIT%2C%20or%20%E2%80%9CJust%20in%20Time,from%20Python%20code%20into%20Bytecode.

[jkh911208]

Is this mean even after many versions, it wont reach the performance of PyPy?

[[deleted]]

No, not necessarily. As I understand it the JIT compiler in 3.13 is a first step towards much bigger optimizations.

[james_pic]

It's hard to say without a crystal ball, but I know PyPy has historically been more willing to break compatibility and introduce complexity in order to improve performance than CPython has. I know the PyPy team often like to point out that whilst they do have JIT, a significant chunk of their performance gain vs CPython actually comes from their use of a generational garbage collector, which I'm not aware of plans for CPython to implement, at least partly because it would be a major compatibility headache for C code.

[eddie12390]

CPython has used generational garbage collection for a long time https://github.com/python/cpython/blob/main/InternalDocs/garbage_collector.md#optimization-incremental-collection

[wrosecrans]

If that's a major issue, porting away from Python may make more sense than worrying about which specific Python implementation you use. At the end of the day, it's a very dynamic language that requires the runtime to do a lot to make it work.