this post was submitted on 10 Jul 2025
70 points (93.8% liked)

Python

7306 readers
2 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

📅 Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

🐍 Python project:
💓 Python Community:
✨ Python Ecosystem:
🌌 Fediverse
Communities
Projects
Feeds

founded 2 years ago
MODERATORS
erlingur@programming.dev
jnovinger@programming.dev
norambna@programming.dev
70
Despite 30 months work, core developer says Python's JIT compiler is often slower than the interpreter (devclass.com)
submitted 1 week ago by cm0002@programming.dev to c/python@programming.dev
30 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] Narann@jlai.lu 7 points 1 week ago (3 children)

Python typing system is the reason of its huge flexibility, but as many other scripting language, it’s also what makes it so hard to optimize.

I have no idea how you can change that without bringing some “JIT-oriented” features inside the Python language itself.

I still hope for the best, but I’m unsure we will be able to see an efficient JIT system inside CPython soon.

PyPy had to rewrite the whole Python implementation in a JIT focused way, and even with that, they are (not uncommon) cases when PyPy is slower.

[–] Corbin@programming.dev 3 points 1 week ago

I gather that you don't actually use PyPy much. On average, I expect PyPy to deliver over a 3x speedup. The main issue is that people have built upon slow libraries like Numpy that only seem fast because CPython is even slower.

The reason that CPython cannot have a JIT added on is architectural and political. The CPython core team refuses to learn lessons from PyPy.

load more comments (2 replies)