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 ronaldoussoren
Recipients bquinlan, mustafaquraish, ned.deily, pitrou, ronaldoussoren
Date 2020-11-07.09:28:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1604741318.31.0.030156690088.issue42281@roundup.psfhosted.org>
In-reply-to
Content
In 3.8 the spawn method for multiprocessing changed from "fork" to "spawn" (see https://docs.python.org/3/whatsnew/3.8.html#multiprocessing).

A side effect of this is that the module gets executed again in the child processes (the same as on Windows).

The reason for this change is that multiple higher level APIs, some of which used by the Python implementation, are are not safe to use with the "fork" spawning strategy (as in: causing crashing when using the fork strategy).
History
Date User Action Args
2020-11-07 09:28:38ronaldoussorensetrecipients: + ronaldoussoren, bquinlan, pitrou, ned.deily, mustafaquraish
2020-11-07 09:28:38ronaldoussorensetmessageid: <1604741318.31.0.030156690088.issue42281@roundup.psfhosted.org>
2020-11-07 09:28:38ronaldoussorenlinkissue42281 messages
2020-11-07 09:28:38ronaldoussorencreate