| ▲ | jonathaneunice a day ago | ||||||||||||||||
Very nice. I've loved PyPy as a way to run Python faster, but it only got to Python 3.12 this September, and that's still beta (https://pypy.org/posts/2026/10/pypy-v801-release.html). That's about 3 years after CPython's 3.12. JIT in CPython itself seems on-again, off-again, so great news that an external approach might be able to take up some slack. | |||||||||||||||||
| ▲ | gudzpoz 21 hours ago | parent | next [-] | ||||||||||||||||
As per the comments from Ken Jin (CPython JIT developer) on the article (at the bottom of the page), the way yk is integrated with CPython isn't really that "external" though: they make use of the existing CPython JIT's tracer, micro optimizations, etc., basically only replacing the copy-and-patch backend. So yk will have to maintain the whole CPython JIT patch (sans copy-and-patch) if they want to retain the same performance after the removal of the JIT compiler from CPython[1]. | |||||||||||||||||
| |||||||||||||||||
| ▲ | istjohn a day ago | parent | prev [-] | ||||||||||||||||
I believe the JIT project in CPython has been scrapped, at least officially. | |||||||||||||||||
| |||||||||||||||||