[issue8713] multiprocessing needs option to eschew fork() under Linux
Richard Oudkerk
report at bugs.python.org
Thu Dec 27 22:07:56 CET 2012
Richard Oudkerk added the comment:
> The safest default would be fork+exec though we need to implement the
> fork+exec code as a C extension module or have it use subprocess (as I
> noted in the mb_fork_exec.patch review).
That was an old version of the patch.
In the branch
http://hg.python.org/sandbox/sbt#spawn
_posixsubprocess is used instead of fork+exec, and all unnecessary fds are closed. See
http://hg.python.org/sandbox/sbt/file/8f08d83264a0/Lib/multiprocessing/popen_spawn_posix.py
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8713>
_______________________________________
More information about the Python-bugs-list
mailing list