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 gregory.p.smith
Recipients barry, davin, gregory.p.smith, josh.r, kapilt, lukasz.langa, miss-islington, ned.deily, pablogsal, pitrou, ronaldoussoren, tdsmith, vstinner
Date 2019-05-28.23:18:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
There is a multiprocessing spawn method on Python 2.7.  And we should never do such a crazy huge feature backport.

IMNSHO - We should not change the default in 3.7 either.  That is a notable behavior change.  That decision is entirely up to Ned (RM).  If people are using an OS that changes behavior out from underneath their application between minor OS version upgrades, they should take that up with the OS vendor.  We cannot workaround this fundamental problem.

Applications and libraries will still need to support a slew of Python versions and OS versions, so they're all going to need to be modified to explicitly request the "spawn" method from multiprocessing on macOS anyways.  So there seems little point in changing the default within a patch release 3.7.4.
Date User Action Args
2019-05-28 23:18:24gregory.p.smithsetrecipients: + gregory.p.smith, barry, ronaldoussoren, pitrou, vstinner, ned.deily, lukasz.langa, josh.r, tdsmith, davin, pablogsal, miss-islington, kapilt
2019-05-28 23:18:24gregory.p.smithsetmessageid: <>
2019-05-28 23:18:24gregory.p.smithlinkissue33725 messages
2019-05-28 23:18:24gregory.p.smithcreate