[issue21372] multiprocessing.util.register_after_fork inconsistency

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 __

[issue21372] multiprocessing.util.register_after_fork inconsistency

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: -> r

[issue21372] multiprocessing.util.register_after_fork inconsistency

Changes by Ned Deily : -- nosy: +sbt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/ma

[issue21372] multiprocessing.util.register_after_fork inconsistency

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 d