Author trcarden
Recipients trcarden
Date 2015-06-25.18:19:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1435256394.21.0.131332757316.issue24512@psf.upfronthosting.co.za>
In-reply-to
Content
We were tracking down a bug the other day that was rather hard to find involving a forking a process that had both a primary thread and a logging thread. The docs clearly state that forking a multithreaded process is "problematic" https://docs.python.org/3.4/library/multiprocessing.html#contexts-and-start-methods

However given that it is very simple to check if the process currently has multiple threads at the time of the forking operation and that its almost never safe to do so with multiple running threads I was wondering if it made sense to add a message that warned that a unsafe operation (forking a multithreaded process without the forkserver option) was occurring.
History
Date User Action Args
2015-06-25 18:19:54trcardensetrecipients: + trcarden
2015-06-25 18:19:54trcardensetmessageid: <1435256394.21.0.131332757316.issue24512@psf.upfronthosting.co.za>
2015-06-25 18:19:54trcardenlinkissue24512 messages
2015-06-25 18:19:53trcardencreate