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 neologix, r.david.murray, sbt, steinn
Date 2014-05-14.13:55:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1400075757.47.0.776562799119.issue21342@psf.upfronthosting.co.za>
In-reply-to
Content
As a historical note, the docs are probably correct...but at some point relatively recently we fixed the inconsistency in what was raised in the thread and threading modules, but obviously no one noticed that multiprocessing had the same issue.  It could be that a comment should be added to the thread/threading code mentioning the multiprocessing clones, and vice versa.  Or perhaps the code can be unified?  I suspect the clones exist primarily because multiprocessing was originally an external project.
History
Date User Action Args
2014-05-14 13:55:57r.david.murraysetrecipients: + r.david.murray, neologix, sbt, steinn
2014-05-14 13:55:57r.david.murraysetmessageid: <1400075757.47.0.776562799119.issue21342@psf.upfronthosting.co.za>
2014-05-14 13:55:57r.david.murraylinkissue21342 messages
2014-05-14 13:55:57r.david.murraycreate