RetroSearch Browse

Wed Apr 29 11:13:03 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-April/139618.html

Yury Selivanov wrote:

> 3. GenObject __iter__ and __next__ raise error
> *only* if it has CO_NATIVE_COROUTINE flag.  So
> iter(), next(), for..in aren't supported only
> for 'async def' functions (but will work ok
> on asyncio generator-based coroutines)

What about new 'async def' code called by existing
code that expects to be able to use iter() or
next() on the future objects it receives?

> 4. 'yield from' *only* raises an error if it yields a
> *coroutine with a CO_NATIVE_COROUTINE*
> from a regular generator.

Won't that prevent some existing generator-based
coroutines (ones not decorated with @coroutine)
from calling ones implemented with 'async def'?

-- 
Greg

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-April/139618.html below:

[Python-Dev] PEP 492: async/await in Python; v3