Marc Schlaich added the comment:
Your statement is not correct, it does work on Windows (where fork is not
available) if you register the hook on module level instead of in `__main__`.
--
___
Python tracker rep...@bugs.python.org
Richard Oudkerk added the comment:
register_after_fork() is intentionally undocumented and for internal use.
It is only run when starting a new process using the fork start method
whether on Windows or not -- the fork in its name is a hint.
--
resolution: - not a bug
stage: -
New submission from Marc Schlaich:
multiprocessing.util.register_after_fork does not behave consistently on
Windows because the `_afterfork_registry` is not transferred to the subprocess.
The following example fails on Windows while it works perfectly on Linux:
import multiprocessing.util
Changes by Ned Deily n...@acm.org:
--
nosy: +sbt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21372
___
___
Python-bugs-list mailing list
