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 r.david.murray
Recipients davin, eryksun, neologix, pietvo, pitrou, r.david.murray, sbt, tim.peters
Date 2016-07-14.16:36:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As far as muliprocessing's "mentality" goes, it aims to provide the *same* API as Threading, so it is logical that it should preserve threading's behavior with respect to child threads in a process, rather than violating threading's model.  Anything else is counter-intuitive to a python programmer, as demonstrated by this issue and Tim's comments :)
Date User Action Args
2016-07-14 16:36:43r.david.murraysetrecipients: + r.david.murray, tim.peters, pitrou, pietvo, neologix, sbt, eryksun, davin
2016-07-14 16:36:43r.david.murraysetmessageid: <>
2016-07-14 16:36:43r.david.murraylinkissue18966 messages
2016-07-14 16:36:43r.david.murraycreate