[issue33544] Asyncio Event.wait() is a hold over from before awaitable, and should be awaitable

Change by Andrew Svetlov : -- resolution: -> rejected stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue33544] Asyncio Event.wait() is a hold over from before awaitable, and should be awaitable

Andrew Svetlov added the comment: -1 for the proposal -- ___ Python tracker ___

[issue33544] Asyncio Event.wait() is a hold over from before awaitable, and should be awaitable

Yury Selivanov added the comment: > Deprecating Event.wait would be incorrect because Event was designed to mimic > the threading.Event class which has a (blocking) wait() method[1]. This is rather important. I'd like to continue maintaining this similarity. Adding

[issue33544] Asyncio Event.wait() is a hold over from before awaitable, and should be awaitable

Hrvoje Nikšić added the comment: Deprecating Event.wait would be incorrect because Event was designed to mimic the threading.Event class which has a (blocking) wait() method[1]. Supporting `await event` is still worthwhile, though. [1]

[issue33544] Asyncio Event.wait() is a hold over from before awaitable, and should be awaitable

Change by Jason Fried : -- keywords: +patch pull_requests: +6584 stage: -> patch review ___ Python tracker ___

[issue33544] Asyncio Event.wait() is a hold over from before awaitable, and should be awaitable

Jason Fried added the comment: Removed Condition from this request, because it has an __await__ method for supporting the the deprecated pattern with async cond: I'll open a different bug, for Condition behavior for 3.9 when we can remove the deprecated pattern.