This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients neologix, pietvo, pitrou, sbt
Date 2013-09-08.17:40:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1378662056.15.0.916424691722.issue18966@psf.upfronthosting.co.za>
In-reply-to
Content
That's because multiprocessing exits child processes with os._exit(), not sys.exit().

The fix would be trivial (call threading._shutdown() before os._exit()), but I don't know if that's something we want to do. After all there are many things in the Python shutdown procedure that we may want to similarly replicate in multiprocessing children, such as calling atexit handlers. This screams for a more general solution, IMHO.
History
Date User Action Args
2013-09-08 17:40:56pitrousetrecipients: + pitrou, pietvo, neologix, sbt
2013-09-08 17:40:56pitrousetmessageid: <1378662056.15.0.916424691722.issue18966@psf.upfronthosting.co.za>
2013-09-08 17:40:56pitroulinkissue18966 messages
2013-09-08 17:40:56pitroucreate