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, lukasz.langa, miss-islington, ned.deily, pablogsal, pitrou, ronaldoussoren, vstinner
Date 2019-05-05.15:44:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Victor raises an important question:  should the *default* start behavior be made consistent across platforms?  Assuming we change it on MacOS, the default start behavior on Windows and MacOS will be spawn but the default start behavior on Linux and FreeBSD (among others) will be fork.

Reasons to consider such a breaking change:
* This inconsistency in default start behavior on different platforms (Windows versus not) has historically been a significant source of confusion for many, many users.
* These days, the majority of users are not already familiar with the rule "fork-before-creating-threads" and so are surprised and confused when they fork a process that already has spun up multiple threads and bad things happen.
* We are changing the default on one platform (MacOS), which should prompt us to consider how are defaults are set elsewhere.

Reasons to reject such a breaking change:
* Though changing the default does not break everyone's code everywhere, it will require changes to any code that depends upon the default start method AND depends upon data/functions/stuff from the parent to also be present in the forked child process.
Date User Action Args
2019-05-05 15:44:41davinsetrecipients: + davin, barry, ronaldoussoren, pitrou, vstinner, ned.deily, lukasz.langa, pablogsal, miss-islington, kapilt
2019-05-05 15:44:41davinsetmessageid: <>
2019-05-05 15:44:41davinlinkissue33725 messages
2019-05-05 15:44:40davincreate