Author ncoghlan
Recipients Olivier.Grisel, brett.cannon, eric.snow, larry, ncoghlan, pitrou, python-dev, sbt
Date 2013-12-15.12:43:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1387111424.46.0.555026189273.issue19946@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2013-12-15 12:43:44ncoghlansetrecipients: + ncoghlan, brett.cannon, pitrou, larry, python-dev, sbt, eric.snow, Olivier.Grisel
2013-12-15 12:43:44ncoghlansetmessageid: <1387111424.46.0.555026189273.issue19946@psf.upfronthosting.co.za>
2013-12-15 12:43:44ncoghlanlinkissue19946 messages
2013-12-15 12:43:44ncoghlancreate