# Python JIT not yet fast

**URL:** <https://discourse.julialang.org/t/python-jit-not-yet-fast/130606>\
**Category:** Offtopic\
**Created:** [July 10, 2025, 12:55pm UTC](https://discourse.julialang.org/t/python-jit-not-yet-fast/130606 "2025-07-10T12:55:16Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [July 10, 2025, 3:41pm UTC](https://discourse.julialang.org/t/python-jit-not-yet-fast/130606/7 "2025-07-10T15:41:18Z")

</div>

This kind of topic has come up many, many times already.

See many previous discussions of this topic linked in [JIT Compiler for CPython - #4 by stevengj](https://discourse.julialang.org/t/jit-compiler-for-cpython/108055/4) e.g. why previous attempts at a Python JIT compiler failed: [Julia motivation: why weren't Numpy, Scipy, Numba, good enough? - #3 by kristoffer.carlsson](https://discourse.julialang.org/t/julia-motivation-why-werent-numpy-scipy-numba-good-enough/2236/3)

---

_[View the full topic](https://discourse.julialang.org/t/python-jit-not-yet-fast/130606)._