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 ncoghlan
Recipients asvetlov, brett.cannon, gvanrossum, martin.panter, ncoghlan, vstinner, yselivanov
Date 2016-01-12.00:35:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The patch looks good to me, but I'd like to see the error message convey two points:
- the coroutine has already terminated (regardless of how that happened)
- the calling code attempted to resume it anyway

That is, something like "Cannot resume terminated coroutine", rather than specifically referring to "await".

After all, waiting for the result with "await" is only one way to terminate a coroutine - you can also get there with direct calls to next(), send(), throw() and close().
Date User Action Args
2016-01-12 00:35:00ncoghlansetrecipients: + ncoghlan, gvanrossum, brett.cannon, vstinner, asvetlov, martin.panter, yselivanov
2016-01-12 00:35:00ncoghlansetmessageid: <>
2016-01-12 00:35:00ncoghlanlinkissue25887 messages
2016-01-12 00:35:00ncoghlancreate