Nick Coghlan added the comment:
Bumping the priority on this, as multiprocessing is currently creating invalid
child processes by failing to set __main__.__spec__ appropriately.
The attached patch is designed to get us started down that path. It's currently
broken, but I need feedback from folks that know the multiprocessing code
better than I do in order to know where best to start poking and prodding.
With the patch, invoking regrtest directly still works:
./python Lib/test/regrtest.py -v test_multiprocessing_spawn
But relying on module execution fails:
./python -m test -v test_multiprocessing_spawn
I appear to be somehow getting child processes where __main__.__file__ is set,
but __main__.__spec__ is not.
----------
nosy: +larry
priority: low -> release blocker
Added file:
http://bugs.python.org/file33146/issue19946_pep_451_multiprocessing.diff
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue19946>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
