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 eryksun
Recipients davin, eryksun, neologix, pietvo, pitrou, sbt, tim.peters
Date 2016-07-14.02:50:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1468464634.44.0.937870213896.issue18966@psf.upfronthosting.co.za>
In-reply-to
Content
> Per Eryk's point about the difference in multiprocessing's behavior
> when using spawn vs. fork, the explanation for why it's done that
> way is also described in the DeveloperWorks article I mentioned above.

Please spell this out for me. Why can't the "fork" and "forkserver" variations call sys.exit(), and thus Py_Finalize? I don't see why it's OK to call the _shutdown function in Lib/threading.py from a spawned child but not a forked child.
History
Date User Action Args
2016-07-14 02:50:34eryksunsetrecipients: + eryksun, tim.peters, pitrou, pietvo, neologix, sbt, davin
2016-07-14 02:50:34eryksunsetmessageid: <1468464634.44.0.937870213896.issue18966@psf.upfronthosting.co.za>
2016-07-14 02:50:34eryksunlinkissue18966 messages
2016-07-14 02:50:34eryksuncreate