Live data from Hacker News

PyPy-STM 2.5.1 released

morepypy.blogspot.com

11–13 of 13 posts

Re: PyPy-STM 2.5.1 released

#11

I might be way off here, but does PyPy-STM works at all with the new stdlib asyncio? I mean, the whole purpose of asyncio is running non-blocking I/O in a single thread and delegate blocking CPU-bound executions to other threads (with the run_in_executor method), but it would be awesome to share the asyncio loop event between multiple threads. I don't know if this is possible though.

asyncio would need some work in order to be trully parallelizable on top of pypy-stm. You would need to go around and eliminate all the global state that all the elements are modifying. But in principle it should work (requires work though)

Re: PyPy-STM 2.5.1 released

#12

Is PyPy basically going to replace the regular CPython runtime that people currently consider "Python"?

In PyPy's FAQ, the answer to the question "Is PyPy a drop in replacement for CPython?" is "Almost!"

... followed by a few paragraphs of details about why it is "almost".[1]

Their caveats seem to match up to several of Guido van Rossum's reservations about PyPy back in 2012 (summary here [2])

In the last 3 years there have been significant improvements with PyPy3 and C extension support, so it's getting closer but I would imagine it will take a few more iterations to from "almost" to "definitely".

I personally believe in PyPy's long-term future, they've done amazing work and think it is worthwhile even if CPython remains the reference platform.

[1] http://doc.pypy.org/en/latest/faq.html#is-pypy-a-drop-in-rep...

[2] http://stackoverflow.com/questions/12867263/why-wasnt-pypy-i...

Post reply on HN