Author fried
Recipients asvetlov, fried, lukasz.langa, yselivanov
Date 2018-05-16.16:57:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526489874.13.0.682650639539.issue33544@psf.upfronthosting.co.za>
In-reply-to
Content
wait is a very overloaded word in asyncio.  Events and Conditions are not consistent with the rest of asyncio.  

Why don't Future and Task have wait() methods? well because they are awaitable

Some subjective reasoning:
Every time I go to use one of these things, I attempt to await them like everything else in the Asyncio world and get a nice exception for it.

   await event

vs

   await event.wait()

I propose we make conditions and events awaitable and deprecate the .wait or at-least remove it from the documentation.
History
Date User Action Args
2018-05-16 16:57:54friedsetrecipients: + fried, asvetlov, lukasz.langa, yselivanov
2018-05-16 16:57:54friedsetmessageid: <1526489874.13.0.682650639539.issue33544@psf.upfronthosting.co.za>
2018-05-16 16:57:54friedlinkissue33544 messages
2018-05-16 16:57:54friedcreate