‘Twas the night before Christmas, and all the developers were taking a break from their work on the code. The Continuous Integration system was carefully checking Pull Requests, hoping for those green checkmarks. As everyone settled down for the night, a sudden commotion in the PRs tab caught their attention. They quickly opened GitHub to investigate the matter. The noise led them to CPython, where they discovered something unexpected: a JIT. It was rapidly optimizing the code, making it faster and more efficient. Excited, they watched YouTube videos and read white papers to understand its capabilities. With a sense of awe, they realized that they didn’t need to write all the code themselves; the JIT could do it for them. The support for different platforms, from ARM64 Macs to 32-bit PCs, was impressive. The JIT even ran tests flawlessly, without any runtime dependencies. It was mostly build-time Python with strict static typing, making maintenance easier. However, there were still areas that needed improvement, such as optimizing the generated code and implementing new calling conventions. But the developers were determined and skilled, and they configured the build to enable the experimental JIT. With their approval, the JIT took flight, promising a brighter future for Python performance.
https://github.com/python/cpython/pull/113465