12 comments

[ 5.8 ms ] story [ 41.1 ms ] thread
Easier pypy with minimal effort

https://github.com/fijal/jitpy

That project hasn't been updated in 6 years
This is amazing, and obvious in retrospect. Gradual compilation can be adopted, well, gradually, without breaking existing code. 100% upside, 0% downside. PyPy team should consider making this delivery mode the #1 priority. Even worth reconsidering the object management impedance as well, and go for 100% compatibility with CPython object model. I suspect this would have a small runtime cost, but a would be a huge boon for smooth risk-free adoption.
Back in Python2 days, you just slam "import psyco" and your code magically goes faster. The pysco authors went ahead and invented pypy.

Ambitious project, but less popularity.

It’s probably a testament to the type of software I typically develop with Python, but I’ve never felt the urge to use PyPy. Even if it’s faster with zero effort, it’s still different.

Any time performance has been a concern that application was in Java or Go (for me).

(Pypy also supports Python 2 and will for the foreseeable future.)
Why’d they name it PyPy, it sounds phonetically exactly like PyPi. aaaahhh this is going to be so confusing
Phonetically pypi is pronounced py-p-i where as pypy is pie-pie :)
How compatible is it nowadays with Numpy, Scipy and the ML toolkits?
I just wanted to thank Real Python folks for their excellent free articles. I remember how eye-opening their article about for loops[0] was for me after using Python for a couple of years.

I wish there were equivalent websites for other languages and technologies like Android, Flutter, and Julia.

[0]: https://realpython.com/python-for-loop/

Will it still be useful in auto scaling clouds of containers? Or will warmup times stall requests every time a container comes up?