➜

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 gregory.p.smith
Recipients Albert.Zeyer, gregory.p.smith
Date 2017-10-20.20:14:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1508530469.41.0.213398074469.issue31814@psf.upfronthosting.co.za>
In-reply-to
Content 
Using new syscalls for _posixsubprocess.c would be a feature so it would be limited to 3.7+ if done at all.

My gut feeling is that the real bug is in *any* library code that uses pthread_atfork() in a non thread safe manner.  That code is fundamentally broken as it is placing a burden upon the entire application that it lives within that the application and no other libraries may use threads or if it does that it may not launch subprocesses.

That is unrealistic.  So I'd blame OpenBlas and OpenMP.

Supporting alternate system calls seems like it would just paper over the issue of improper use of pthread_atfork rather than address the fundamental problem.
History
Date User Action Args
2017-10-20 20:14:29gregory.p.smithsetrecipients: + gregory.p.smith, Albert.Zeyer
2017-10-20 20:14:29gregory.p.smithsetmessageid: <1508530469.41.0.213398074469.issue31814@psf.upfronthosting.co.za>
2017-10-20 20:14:29gregory.p.smithlinkissue31814 messages
2017-10-20 20:14:29gregory.p.smithcreate