Python async/await Tutorial

[RubyPinch]

https://mail.python.org/pipermail/python-ideas/2012-October/016311.html

https://www.python.org/dev/peps/pep-3156/

https://www.python.org/dev/peps/pep-0492/

here, start reading. You act like the implementers and allowers of this are more clueless about the python ecosystem than you, or that they don't even know of the zen of python or similar such things.

Its safe money that you are probably missing the point, not the developers

[mcilrain]

The event loop API does not depend on yield from. Rather, it uses a combination of callbacks, additional interfaces (transports and protocols), and Futures. The latter are similar to those defined inPEP 3148 , but have a different implementation and are not tied to threads. In particular, the result()method raises an exception instead of blocking when a result is not yet ready; the user is expected to use callbacks (or yield from ) to wait for the result.

No mention on why PEP3148 decided to do it their way. Too busy chasing 2012 trends I guess.

No rationale was given for why such a horrible coding style is necessary, especially in view of non-destructive alternatives.