Message256567
| 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 |
<1450310002.82.0.504877245218.issue25887@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> 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 |
|