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 Dima.Tisnek
Recipients Dima.Tisnek, asvetlov, terry.reedy, yselivanov
Date 2019-06-10.01:48:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1560131336.2.0.0164219241116.issue37172@roundup.psfhosted.org>
In-reply-to
Content
Hi Terry,

Yes, I have a specific suggestion:

The error `RuntimeError: await wasn't used with future` is misleading.
I'm not sure if changing error text is enough.
I think that Future.__await__ should be fixed; I think that `await f` should be idempotent, that the same exception should be raised in single and double await examples.
History
Date User Action Args
2019-06-10 01:48:56Dima.Tisneksetrecipients: + Dima.Tisnek, terry.reedy, asvetlov, yselivanov
2019-06-10 01:48:56Dima.Tisneksetmessageid: <1560131336.2.0.0164219241116.issue37172@roundup.psfhosted.org>
2019-06-10 01:48:56Dima.Tisneklinkissue37172 messages
2019-06-10 01:48:56Dima.Tisnekcreate