[issue11240] Running unit tests in a command line tool leads to infinite loop with multiprocessing on Windows
Amaury Forgeot d'Arc
report at bugs.python.org
Fri Feb 18 01:51:56 CET 2011
Amaury Forgeot d'Arc <amauryfa at gmail.com> added the comment:
> It seems as if the multiprocessing module is starting new Windows
> processes by duplicating the command line of the original process.
It does not. The spawned processes use the command::
python.exe -c 'from multiprocessing.forking import main; main()' --multiprocessing-fork [handle#]
And only after, the multiprocessing machinery overrides sys.argv with the same value as the initial process.
There is certainly some code in one of your modules that starts running the tests.
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list