This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

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 <>
> 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.
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: <>
2021-06-04 21:43:50chris.jerdoneklinkissue38323 messages
2021-06-04 21:43:50chris.jerdonekcreate