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 barry
Recipients barry, davin, josh.r, kapilt, lukasz.langa, miss-islington, ned.deily, pablogsal, pitrou, ronaldoussoren, vstinner
Date 2019-05-14.01:39:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
On May 10, 2019, at 04:07, Josh Rosenberg <> wrote:
> I've seen far too many cases where Python code targeting Linux intentionally uses the COW benefits of fork for multiprocessing to think it would be a good idea to change the default start method there without *some* sort of deprecation period.

We need to resolve this for 3.8, and given that I think we have clear consensus to change the default on macOS to spawn to avoid the crashes, let’s do that.  We’ll need to update the documentation.

Then if we don’t have consensus to change the default on Linux, let’s issue a DeprecationWarning for the default ‘fork’ method in 3.8 and change it to ‘spawn' in 3.9.

Do we want to issue a warning on set_start_method(‘fork’) on macOS, given that it’s unlikely to be safe?
Date User Action Args
2019-05-14 01:39:45barrysetrecipients: + barry, ronaldoussoren, pitrou, vstinner, ned.deily, lukasz.langa, josh.r, davin, pablogsal, miss-islington, kapilt
2019-05-14 01:39:45barrylinkissue33725 messages
2019-05-14 01:39:45barrycreate