[issue24080] asyncio.Event.wait() Task was destroyed but it is pending

Andrew Svetlov added the comment: Duplicate for #39622 -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> KeyboardInterrupt is ignored when await asyncio.sleep(0) ___ Python tracker

[issue24080] asyncio.Event.wait() Task was destroyed but it is pending

Change by Irit Katriel : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue24080] asyncio.Event.wait() Task was destroyed but it is pending

Marco Paolini added the comment: KeyboardInterrupt is not handled gently by asyncio (see https://groups.google.com/d/msg/python-tulip/sovg7EIBoXs/m7U-0UXqzSQJ) you could cancel all tasks in the signal handler: ... def sig_interrupt(): print('interrupt') for task in asyncio.Task.all_ta

[issue24080] asyncio.Event.wait() Task was destroyed but it is pending

New submission from Matt Johnston: asyncio.Event.wait() doesn't seem to be cancelled by asyncio.wait_for(). Ctrl-c in the attached example produces output below. I'm not certain the code is correct though the documentation for wait_for() suggests it should work. Without the wait_for() it doesn