News for hackers. Stuff that matters.
Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by maxbond on Sunday September 27, 2020 @03:04AM (#24604817)
The PyPy website suggests this is the case.

https://www.pypy.org/features.html

> Our main executable comes with a Just-in-Time compiler. It is really fast in running most benchmarks—including very large and complicated Python applications, not just 10-liners.

> There are two cases that you should be aware where PyPy will not be able to speed up your code:

> Short-running processes: if it doesn't run for at least a few seconds, then the JIT compiler won't have enough time to warm up.

> If all the time is spent in run-time libraries (i.e. in C functions), and not actually running Python code, the JIT compiler will not help.

Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by moonchild on Sunday September 27, 2020 @03:35AM (#24604933)
Does it? It looks to me like it indicates performance will be the same when calling c functions.
Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by gridlockd on Sunday September 27, 2020 @04:05AM (#24605043)
It depends on how the C functions are called. CPython extension modules either don't work or have high overhead.

CFFI-based modules should work without a big penalty, but these are generally slower than extension modules.