[issue19946] Handle a non-importable __main__ in multiprocessing
Zachary Ware
report at bugs.python.org
Thu Dec 19 04:55:20 CET 2013
Zachary Ware added the comment:
The problem on Windows at least is that the skips for the 'fork' and 'forkserver' start methods aren't firing due to setUpClass being improperly set up in MultiProcessingCmdLineMixin: it's not decorated as a classmethod and the 'u' is lower-case instead of upper. Just fixing that makes for some unusual output ("skipped '"fork" start method not available'" with no indication of which test was skipped) and a variable number of tests depending on available start methods, so a better fix is to just do the check in setUp.
Unrelated to the failure, but we're also in the process of moving away from using test_main(), preferring unittest.main().
The attached patch addresses both, passes on Windows and Linux, and I suspect should help on OpenIndiana as well judging by the tracebacks it's giving.
----------
nosy: +zach.ware
Added file: http://bugs.python.org/file33201/issue19946.diff
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19946>
_______________________________________
More information about the Python-bugs-list
mailing list