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 vtsozik
Recipients christian.heimes, vtsozik
Date 2019-02-05.23:13:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1549408412.86.0.0795671687567.issue35902@roundup.psfhosted.org>
In-reply-to
Content
Thank you for your reply. I understand that forking and threads do not mix well if developer is not careful and child doesn't clear/reset synchronization variables inherited from parent. However this is not the case in provided code sample. The answer to my question is probably related to the fact that only main thread handles signaling by default in POSIX. But in the provided example parent background thread becomes main in the child. In parent it doesn't matter if waitpid blocks on main or background thread. The only thing really matters if code forks from main or background threads.
History
Date User Action Args
2019-02-05 23:13:34vtsoziksetrecipients: + vtsozik, christian.heimes
2019-02-05 23:13:32vtsoziksetmessageid: <1549408412.86.0.0795671687567.issue35902@roundup.psfhosted.org>
2019-02-05 23:13:32vtsoziklinkissue35902 messages
2019-02-05 23:13:32vtsozikcreate