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.07:11:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1452582663.25.0.234783824856.issue25887@psf.upfronthosting.co.za>
In-reply-to
Content
I expect whatever message we use will become a Stack Overflow question in fairly short order, so "good enough" is almost certainly good enough here, and I'm massively overthinking the problem :)

However, combining my last suggestion with a variant of Martin's would give us:

    "Cannot reuse already awaited coroutine"

The generic "reuse" both eliminated the repetition of "await", and also gets us away from worrying about exactly what the caller was doing.
History
Date User Action Args
2016-01-12 07:11:03ncoghlansetrecipients: + ncoghlan, gvanrossum, brett.cannon, vstinner, asvetlov, martin.panter, yselivanov
2016-01-12 07:11:03ncoghlansetmessageid: <1452582663.25.0.234783824856.issue25887@psf.upfronthosting.co.za>
2016-01-12 07:11:03ncoghlanlinkissue25887 messages
2016-01-12 07:11:03ncoghlancreate