[New-bugs-announce] [issue21372] multiprocessing.util.register_after_fork inconsistency
Marc Schlaich
report at bugs.python.org
Mon Apr 28 10:16:04 CEST 2014
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
def hook(*args):
print (args)
def func():
print ('func')
if __name__ == '__main__':
multiprocessing.util.register_after_fork(hook, hook)
p = multiprocessing.Process(target=func)
p.start()
----------
components: Windows
messages: 217347
nosy: schlamar
priority: normal
severity: normal
status: open
title: multiprocessing.util.register_after_fork inconsistency
type: behavior
versions: Python 2.7, Python 3.3, Python 3.4
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21372>
_______________________________________
More information about the New-bugs-announce
mailing list