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 davin, eryksun, neologix, pietvo, pitrou, sbt, tim.peters
Date 2016-07-14.06:42:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I agree with Tim. Regardless of what OS threads do, Python tries to enforce predictable semantics of its own. There's no reason (apart from historical baggage) to not join Python threads (and only Python threads, of course, not other OS threads) at the shutdown of a child process.

I don't exactly remember why using os._exit() rather than sys.exit() is required in child processes. Presumably it is because we don't want the child to clobber any resources shared with the parent (open files?). This doesn't have to be a binary thing, though: it may as well be os._exit() + a bunch of cleanup steps we know are safe to perform.
Date User Action Args
2016-07-14 06:42:06pitrousetrecipients: + pitrou, tim.peters, pietvo, neologix, sbt, eryksun, davin
2016-07-14 06:42:06pitrousetmessageid: <>
2016-07-14 06:42:06pitroulinkissue18966 messages
2016-07-14 06:42:06pitroucreate