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 asvetlov
Recipients aeros, asvetlov, benjamin.peterson, vstinner, yselivanov
Date 2019-11-14.11:39:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1573731543.5.0.482622569703.issue38591@roundup.psfhosted.org>
In-reply-to
Content
To be clear: I mean that FastChildWatcher is safe only if all process's code spaws subprocesses by FastChildWatcher.
If ProcessPoolExecutor or direct subprocess calls are used the watcher is unsafe.
If some C extension spawns new processes on its own (e.g. in a separate thread) -- the watcher is unsafe.

I just think that this particular watcher is too dangerous.
History
Date User Action Args
2019-11-14 11:39:03asvetlovsetrecipients: + asvetlov, vstinner, benjamin.peterson, yselivanov, aeros
2019-11-14 11:39:03asvetlovsetmessageid: <1573731543.5.0.482622569703.issue38591@roundup.psfhosted.org>
2019-11-14 11:39:03asvetlovlinkissue38591 messages
2019-11-14 11:39:03asvetlovcreate