asyncio

AsyncIO is part of the core python 3 where gevent is a package (origninally designed for python 2).

Their disagreement is very deep and it's unlikely you could do things in a philosophically gevent way with the asyncIO tools.

You're right about asyncio, but the new async PEP undeniably adds a lot of complication to a story which was already working.

Or between the new async / await and the current asyncio?

Gevent will probably never have a strong dependency on AsyncIO.

I like asyncio in principle, but here we see that addition spawning another addition.

It's not an efficient implementation - it was really meant as a proof of concept that you can use async/await in your own code without any reference to asyncio.

Isn't twisted largely superseded by asyncio?

While I've commented before about how asyncio is still a bit more nascent than I'd like, I'm really excited to see where the community takes it.

Don't look at gevent for Python, look at a responsible async library: asyncio if you like Py3, Twisted if you like Py2 and want something that's very featureful but old-school, Trollius if you wish you could be using asyncio but you're stuck on Py2.

Nah, asyncio (including both the library and these new language features) is a huge simplification of the ecosystem for people writing network code, while people not writing asynchronous code can pretty much ignore it if they want to.

You can handle tens of thousands of simultaneous requests as well, and sometimes even better, in Go, Erlang, Stackless Python, Python 2 with Tornado or gevent, Python 3 with asyncio, Haskell, Java with vert.x or Quasar, nginx with Lua, and many other examples.

There's already a decorator @asyncio.coroutine which "async def" replaces.