Author chris.jerdonek
Recipients aeros, asvetlov, chris.jerdonek, jstasiak, miss-islington, njs, vstinner, yselivanov
Date 2021-06-04.21:43:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1622843030.3.0.407601589819.issue38323@roundup.psfhosted.org>
In-reply-to
Content
> MultiLoopChildWatcher must ensures that the event loop is awaken when it receives a signal by using signal.setwakeup(). This is done by _UnixSelectorEventLoop.add_signal_handler(). Maybe MultiLoopChildWatcher could reuse this function, 

This is the conclusion I came to, too. But changing MultiLoopChildWatcher to use loop.add_signal_handler() would contradict the class's documented purpose and make it the same as SafeChildWatcher. This is why I think a maintainer needs to weigh in. The class's purpose / design might fundamentally not be workable. If it can't be made to work, maybe it should be removed or be documented as susceptible to hangs.
History
Date User Action Args
2021-06-04 21:43:50chris.jerdoneksetrecipients: + chris.jerdonek, vstinner, njs, asvetlov, yselivanov, jstasiak, miss-islington, aeros
2021-06-04 21:43:50chris.jerdoneksetmessageid: <1622843030.3.0.407601589819.issue38323@roundup.psfhosted.org>
2021-06-04 21:43:50chris.jerdoneklinkissue38323 messages
2021-06-04 21:43:50chris.jerdonekcreate