Skip to content

bpo-33725: multiprocessing uses spawn by default on macOS#13603

Merged
vstinner merged 1 commit intopython:masterfrom
vstinner:mp_macos
May 28, 2019
Merged

bpo-33725: multiprocessing uses spawn by default on macOS#13603
vstinner merged 1 commit intopython:masterfrom
vstinner:mp_macos

Conversation

@vstinner
Copy link
Member

@vstinner vstinner commented May 27, 2019

The multiprocessing module now uses the "spawn" start method by
default on macOS.

https://bugs.python.org/issue33725

@vstinner
Copy link
Member Author

cc @warsaw @applio @pitrou

@vstinner
Copy link
Member Author

I didn't test my PR. I'm not a multiprocessing expert at all, so I'm not sure that it even does what it is supposed to do :-D

@vstinner
Copy link
Member Author

I tested my PR on macOS: it seems like it works as expected :-)

macbook:master haypo$ ./python.exe
Python 3.8.0a4+ (heads/pr/13603:d117d0f, May 28 2019, 14:37:04) 
[Clang 10.0.0 (clang-1000.10.44.4)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import multiprocessing; multiprocessing.get_context()
<multiprocessing.context.SpawnContext object at 0x1009c9550>

On macOS, the multiprocessing module now uses the "spawn" start
method by default.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments