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 Elad Lahav
Recipients Elad Lahav, dstufft, eric.araujo, gvanrossum, p-ganssle, pitrou, vstinner
Date 2020-03-01.02:51:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1583031116.43.0.826816943319.issue39763@roundup.psfhosted.org>
In-reply-to
Content
"setup.py doesn't use multiprocessing. multiprocessing is super complex. Would it be possible to write a reproducer which doesn't use multiprocessing?"

But the problem is with the handling of fork() by Python modules, and specifically with multi-threaded fork()s. Without multiple processes there is no issue.

And setup.py does use use multiple processes via a thread pool, where each thread calls fork(), if it detects that "make" was invoked with the parallel (-j) option.
History
Date User Action Args
2020-03-01 02:51:56Elad Lahavsetrecipients: + Elad Lahav, gvanrossum, pitrou, vstinner, eric.araujo, dstufft, p-ganssle
2020-03-01 02:51:56Elad Lahavsetmessageid: <1583031116.43.0.826816943319.issue39763@roundup.psfhosted.org>
2020-03-01 02:51:56Elad Lahavlinkissue39763 messages
2020-03-01 02:51:56Elad Lahavcreate