Isn't Python 3 exactly a way to unify the async approaches? (not saying a good/bad way, just a way) We've had a few projects trying to do async in many ways over the years: stackless, gevent, twisted, asyncio, curio, ...

async in Python 3 goes from "there's lots of solutions, which should I choose?" to "there's an obvious solution in standard library (unless you really want something else for a very specific reason)"

The great thing and the awful thing about open source is that anyone can change what it means to be the "Zen of Python."

> There should be one—and preferably only one—obvious way to do it

I feel this can be interpreted many ways. Sure, async means there is more than one way you can do requests to get web data now, and more than one way you should structure your app - but not every app needs to do API calls async, and sometimes the complexity is not worth it.

Other times, yes, of course you need to do requests async. They're taking three minutes each and you have to do twenty of them.

The story of "import this": https://www.wefearchange.org/2010/06/import-this-and-zen-of-...

There's also:

from __future__ import braces

and

import antigravity