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 davin
Recipients barry, davin, kapilt, miss-islington, ned.deily, pitrou, ronaldoussoren, vstinner
Date 2019-03-10.02:58:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As best as I can see, there is no magic bullet to help mitigate this.

At a minimum, I am convinced we need to update the documentation to describe this behavior on MacOS and recommend alternatives.

I continue to give serious thought to the idea of changing the default start method on MacOS from fork to spawn.  This would be a breaking change though one could argue MacOS has already undergone a breaking change.  Is such a change warranted?

The alternative (which does not seem all that appealing) is that we start encouraging everyone to first consider the start method before attempting to use multiprocessing even for their first time.  Providing sensible defaults is to be preferred, but changing the default to reflect a non-trivial change in the underlying platform is still not to be taken lightly.
Date User Action Args
2019-03-10 02:58:29davinsetrecipients: + davin, barry, ronaldoussoren, pitrou, vstinner, ned.deily, miss-islington, kapilt
2019-03-10 02:58:29davinsetmessageid: <>
2019-03-10 02:58:29davinlinkissue33725 messages
2019-03-10 02:58:28davincreate