Message 289908 - Python tracker

➜

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	methane
Recipients	Birne94, methane
Date	2017-03-21.02:41:20
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1490064081.76.0.885430483314.issue29859@psf.upfronthosting.co.za>
In-reply-to

Content
I don't know your patch is worth enough or not. (I dislike fprintf(stderr, ...) at least). But my advice is stop mixing multithreading and fork (except fork+exec). It's almost impossible. While Python has GIL, some extension can release GIL and run any C code. But very vary functions are not fork-safe. Even malloc and printf are unsafe. For more information, see "rational" section in http://pubs.opengroup.org/onlinepubs/009695399/functions/pthread_atfork.html

I don't know your patch is worth enough or not. (I dislike fprintf(stderr, ...) at least).

But my advice is stop mixing multithreading and fork (except fork+exec).
It's almost impossible.

While Python has GIL, some extension can release GIL and run any C code.
But very vary functions are not fork-safe.  Even malloc and printf are unsafe.

For more information, see "rational" section in 
http://pubs.opengroup.org/onlinepubs/009695399/functions/pthread_atfork.html

History
Date	User	Action	Args
2017-03-21 02:41:21	methane	set	recipients: + methane, Birne94
2017-03-21 02:41:21	methane	set	messageid: <1490064081.76.0.885430483314.issue29859@psf.upfronthosting.co.za>
2017-03-21 02:41:21	methane	link	issue29859 messages
2017-03-21 02:41:20	methane	create