-
assigned issue to
- changed title to Utilize spawn or forkserver instead of fork for multiprocessing module
- edited description
Utilize spawn or forkserver instead of fork for multiprocessing module
Issue #20
resolved
Due to new security features in OS X Mojave, we should look into using the spawn
or forkserver
process instead of fork
when creating child processes.
This is documented in: https://bugs.python.org/issue33725
Another workaround is to set the environment variable: export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES
However, I think it may be easier/better long-term to use:
multiprocessing.set_start_method('spawn')
Comments (4)
-
repo owner -
repo owner - edited description
-
repo owner It looks like the consensus on that python bug is that OS X should use
spawn
going forward. I will updatesshreader
to manually specify that. -
repo owner - changed status to resolved
- Log in to comment