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 martin.panter
Recipients asvetlov, brett.cannon, gvanrossum, martin.panter, ncoghlan, vstinner, yselivanov
Date 2016-01-12.02:25:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If the coroutine-iterator is going to raise RuntimeError rather than StopIteration, do you think the __await__() documentation <> should be clarified?

IMO “yield from coroutine_iterator” might be plausable for some strange combination of 3.4 code and a 3.5 coroutine, but I think it would be rare. And if you added a check in __await__() then the using “await” wouldn’t need to rely on next() raising the RuntimeError.
Date User Action Args
2016-01-12 02:25:47martin.pantersetrecipients: + martin.panter, gvanrossum, brett.cannon, ncoghlan, vstinner, asvetlov, yselivanov
2016-01-12 02:25:47martin.pantersetmessageid: <>
2016-01-12 02:25:47martin.panterlinkissue25887 messages
2016-01-12 02:25:47martin.pantercreate