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 yselivanov
Recipients asvetlov, yselivanov
Date 2018-09-24.16:42:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
In-reply-to
Content
asyncio.wait() accepts coroutines, wraps them into Tasks, and later returns those implicitly created Tasks in (done, pending) sets.  This is very confusing to new asyncio users and it's almost impossible to figure out what is going on.  See the first PR to the docs for more info.

Andrew, I think we should deprecate passing coroutines to asyncio.wait() in 3.8, and disallow that in 4.0.
History
Date User Action Args
2018-09-24 16:42:33yselivanovsetrecipients: + yselivanov, asvetlov
2018-09-24 16:42:33yselivanovsetmessageid: <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
2018-09-24 16:42:33yselivanovlinkissue34790 messages
2018-09-24 16:42:33yselivanovcreate