News for hackers. Stuff that matters.

A comment on From Python to Go and Back Again. Parent comment

Re:From Python to Go and Back Again by windlep on Saturday October 17, 2015 @02:03AM (#10403546)
We used Python 2.7 for pypy compatibility. I really dig the new async/await primitives added to Python 3.5 and think the asyncio path is the best path forward. I hope the work to get all the latest asyncio stuff working on PyPy picks up some steam.
[ Parent | on HN ]
Re:From Python to Go and Back Again by bpicolo on Saturday October 17, 2015 @04:02PM (#10405830)
The main issue with asyncio is it is incompatible with some of the best packages in the ecosystem atm, e.g sqlalchemy
[ Parent | on HN ]
Re:From Python to Go and Back Again by sandGorgon on Saturday October 17, 2015 @03:00AM (#10403645)
hey - thanks for replying.

if Pypy + asyncio was available, would you have built everything using that stack ? There have been all these benchmarks that asyncio is so much slower than threads [1] How would you compare that with Go ?

[1] http://techspot.zzzeek.org/2015/02/15/asynchronous-python-an...

[ Parent | on HN ]
Re:From Python to Go and Back Again by kintamanimatt on Saturday October 17, 2015 @07:40AM (#10404103)
For certain things that they probably shouldn't be used for, not across the board.
[ Parent | on HN ]