Author aeros
Recipients aeros, asvetlov, benjamin.peterson, nanjekyejoannah, njs, vstinner, yan12125, yselivanov
Date 2019-11-13.22:54:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1573685693.55.0.389897057051.issue38692@roundup.psfhosted.org>
In-reply-to
Content
> We can merge this PR as is (Benjamin, thanks for working on this!), but I think that as soon as we merge it we should do some refactoring and deprecations.

> The child watchers API has to go. It's confusing, painful to use, it's not compatible with third-party event loops. It increases the API surface without providing us with enough benefits.

+1

> In 3.9 we will use kqueue / pidfd / threads / winapis -- whatever is available, but we never use SIGCHLD by default.

IIRC, we don't use SIGCHLD by default at the moment, since ThreadedChildWatcher is the default child watcher. Should we change the default to be the new PidfdChildWatcher for Linux kernels 5.3+ in Python 3.9, and fallback to ThreadedChildWatcher for systems without pidfd_open()?
History
Date User Action Args
2019-11-13 22:54:53aerossetrecipients: + aeros, vstinner, benjamin.peterson, njs, asvetlov, yselivanov, yan12125, nanjekyejoannah
2019-11-13 22:54:53aerossetmessageid: <1573685693.55.0.389897057051.issue38692@roundup.psfhosted.org>
2019-11-13 22:54:53aeroslinkissue38692 messages
2019-11-13 22:54:53aeroscreate