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 yselivanov
Recipients aeros, asvetlov, vstinner, yselivanov
Date 2019-10-25.19:43:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1572032611.46.0.548029818532.issue38591@roundup.psfhosted.org>
In-reply-to
Content
> but perhaps if we go through with that we should remove MultiLoopChildWatcher from 3.8 (if it's not too late to do so) instead of deprecating it.

I'll leave that up to Andrew to decide, but I'd be +1 to drop it asap, especially if we want to eventually deprecate watchers.  

Speaking of watchers -- big +1 from me to drop them all at some point. I would start as early as 3.9.

Linux has pidfd now, freebsd/macos has kqueue, windows has its own apis for watching processes. Threads can be the backup method for OSes that lack proper APIs for watching multiple processes (without using SIGCHLD etc).
History
Date User Action Args
2019-10-25 19:43:31yselivanovsetrecipients: + yselivanov, vstinner, asvetlov, aeros
2019-10-25 19:43:31yselivanovsetmessageid: <1572032611.46.0.548029818532.issue38591@roundup.psfhosted.org>
2019-10-25 19:43:31yselivanovlinkissue38591 messages
2019-10-25 19:43:31yselivanovcreate