Michel Hidalgo added the comment:
Circling back. I've been giving some thought to this. While this could be fixed
within asyncio.proactor_events.ProactorEventLoop and
asyncio.unix_events._UnixSelectorEventLoop implementations (e.g. calling
signal.set_wakeup_fd once and forwarding s
New submission from Michel Hidalgo :
asyncio.ProactorEventLoop uses a socket.socketpair and signal.set_wakeup_fd to
wake up a loop that's polling I/O. However it does so with no consideration for
file descriptors previously set (i.e. no signal number forwarding). Either by
user code
Michel Hidalgo added the comment:
Sorry for taking so long to reply.
Sure, I would be happy to contribute. We should probably take care of Unix
event loops -- since I opened this ticket I found out those tend to not
cooperate with other signal wakeup file descriptor users either. I am a
