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 ncoghlan
Recipients jnoller, ncoghlan, pitrou
Date 2008-09-01.21:22:16
SpamBayes Score 0.0016318035
Marked as misclassified No
Message-id <1220304137.57.0.970812175873.issue3589@psf.upfronthosting.co.za>
In-reply-to
Content
Given how long I've been using the threading module without realising it
does the same thing, I'm actually prepared to live with the wrapper
functions rather than messing with this so close to release.

As Fredrik noted in the python-dev thread, the threading versions of
these are already explicitly documented as being factory functions
rather than classes (and as a reference to _thread.allocate_lock,
threading.Lock has good reason to be a factory function rather than a
class), so it may be appropriate to do the same thing for multiprocessing.
History
Date User Action Args
2008-09-01 21:22:17ncoghlansetrecipients: + ncoghlan, pitrou, jnoller
2008-09-01 21:22:17ncoghlansetmessageid: <1220304137.57.0.970812175873.issue3589@psf.upfronthosting.co.za>
2008-09-01 21:22:16ncoghlanlinkissue3589 messages
2008-09-01 21:22:16ncoghlancreate