This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author yselivanov
Recipients asvetlov, gvanrossum, martin.panter, ncoghlan, vstinner, yselivanov
Date 2015-12-16.23:53:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> OK, but only for await (not for yield from).

Sure, generators will stay untouched (I'll even add a unittest for that, if we don't have it).

> It should always be valid to create a new coroutine instance. Perhaps you meant:

Correct, Martin, great that you've noticed that!

I'll duplicate the fixed code:

async def coroutine():
    return 123
coro = coroutine()

# In Python 3.5.1:
print(await coro)   # will print 123
print(await coro)   # prints None
print(await coro)   # prints None

# What we want in Python 3.5.2
print(await coro)   # will print 123
print(await coro)   # raises RuntimeError
Date User Action Args
2015-12-16 23:53:22yselivanovsetrecipients: + yselivanov, gvanrossum, ncoghlan, vstinner, asvetlov, martin.panter
2015-12-16 23:53:22yselivanovsetmessageid: <>
2015-12-16 23:53:22yselivanovlinkissue25887 messages
2015-12-16 23:53:22yselivanovcreate