Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.

2recommend
2warn against
Nov 1, 2025first mention
Oct 27, 2026latest mention
Nov 25 – Oct 26
Used forjit performance

Why people recommend it

“The WASI support in CPython has moved along very well”

“Python 3.15 adapts Pypy tracing approach to JIT and there are real performance gains now”

Caveats and dissent

“CPython is clearly not going to happen in this regard”

“The biggest issue has been that CPython exposes its internals to native libraries”

Often compared with

From the makers not counted in the ranking

“I implemented most of the tracing JIT frontend in Python 3.15”

All comments 10

“CPython is clearly not going to happen in this regard”

“The WASI support in CPython has moved along very well”

“Python 3.15 adapts Pypy tracing approach to JIT and there are real performance gains now”

“to get real CPython starting in ~15ms”

“By that definition I think either both have a spec”

“data analysis pipelines are probably still faster in numpy on CPython than pypy.”

“which make it virtually impossible to break compatibility”

The money shot (wish this were included in the blog post): # if defined(_MSC_VER) && !defined(__clang__) # define Py_MUSTTAIL [[msvc::musttail]] # define Py_PRESERVE_NONE_CC __preserve_none # else # define Py_MUSTTAIL __attribute__((musttail)) # define Py_PRESERVE_NONE_CC __attribute__((preserve_none)) # endif https://github.com/python/cpython/pull/143068/files#diff-45baf725df91ed7826458cda8a17c2b4a2e5296504de1ed6a1c

“The biggest issue has been that CPython exposes its internals to native libraries”

“This sort of thing may work totally differently in PyPy”

Threads where it came up

Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.

Keyboard shortcuts
j / kNext / previous item
o or EnterOpen selected item
/Search
g hHome
g tTop
g rRising
g cCategories
tToggle dark mode
?This help