➜

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 lisroach
Recipients lisroach, xtreak
Date 2019-09-27.23:26:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1569626782.82.0.500348249158.issue38161@roundup.psfhosted.org>
In-reply-to
Content 
Looking at this more, I think I want to just remove the current `awaited` object. The PR in asyntest makes it seem pretty cool: https://github.com/Martiusweb/asynctest/issues/64

But I have issue with the naming (await_event is probably better for us), and I'm not sure how to document it well and ensure it's well tested.

With the 3.8 release coming up fast I'd rather remove it for now and then add it back in after some more thought has been given to the feature, instead of getting stuck with a not fully thought out attribute we have to worry about deprecating.
History
Date User Action Args
2019-09-27 23:26:22lisroachsetrecipients: + lisroach, xtreak
2019-09-27 23:26:22lisroachsetmessageid: <1569626782.82.0.500348249158.issue38161@roundup.psfhosted.org>
2019-09-27 23:26:22lisroachlinkissue38161 messages
2019-09-27 23:26:22lisroachcreate