News for hackers. Stuff that matters.

A comment on Async I/O for Python 3 . Parent comment

Re:Async I/O for Python 3 by pekk on Monday March 18, 2013 @03:57PM (#5396739)
Have you actually got any war stories about gevent, or is this all guesswork about how you think it stands to reason that it would be bad?

Do you think this would be relevant if greenlets were adopted as a part of Python?

[ Parent | on HN ]
Re:Async I/O for Python 3 by rdtsc on Monday March 18, 2013 @07:02PM (#5397750)
I have -- we used Twisted (about 10k lines of code). Then switched to eventlet -- and the code reduced to about 5 or 6K. There were some issues with monkey-patching, but tests showed them, and we fixed them.

As someone mentioned, if they instead standardized on greenlet then monkeypatching talk wouldn't make sense.

[ Parent | on HN ]