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 André Caron
Recipients André Caron, asvetlov, brett.cannon, gvanrossum, martin.panter, ncoghlan, vstinner, yselivanov
Date 2016-02-13.21:21:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1455398511.73.0.0805537908264.issue25887@psf.upfronthosting.co.za>
In-reply-to
Content
After thinking about this some more, I think my problem with asyncio.wait() is a bit bigger than the simple fact that coroutine objects cannot be awaited multiple times.  It seems to me like asyncio.wait() is completely broken for coroutine objects as inputs and that multiple awaits on coroutine objects only make that problem worse.

While I still think there is a major benefit API-wise to have await expressions produce the same behaviour for both Futures and coroutine objects, I'm moving that discussion to issue #26357.

http://bugs.python.org/issue26357
History
Date User Action Args
2016-02-13 21:21:51André Caronsetrecipients: + André Caron, gvanrossum, brett.cannon, ncoghlan, vstinner, asvetlov, martin.panter, yselivanov
2016-02-13 21:21:51André Caronsetmessageid: <1455398511.73.0.0805537908264.issue25887@psf.upfronthosting.co.za>
2016-02-13 21:21:51André Caronlinkissue25887 messages
2016-02-13 21:21:51André Caroncreate