[issue47014] ProactorEventLoop ignores Ctrl+C after closing unrelated loop

Change by Andrew Svetlov : -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue47014] ProactorEventLoop ignores Ctrl+C after closing unrelated loop

Andrew Svetlov added the comment: Ctrl-C handling is added by #23057 It uses signal.set_wakeup_fd() https://github.com/asvetlov/cpython/blob/main/Lib/asyncio/proactor_events.py#L631-L634 So, the last event loop steals Ctrl+C handling. Not sure if we can improve it. Running two concurrent

[issue47014] ProactorEventLoop ignores Ctrl+C after closing unrelated loop

New submission from Maximilian Hils : When a (second) ProactorEventLoop is garbage-collected, the current ProactorEventLoop starts to ignore Ctrl+C on Windows until it is woken up. The attached repro shows a minimal example. Uncommenting the `create_task` call or not using a second event