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 sbt
Recipients Sebastian.Noack, asvetlov, jyasskin, kristjan.jonsson, mklauber, pitrou, sbt
Date 2012-09-30.14:00:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1349013626.57.0.524502900149.issue8800@psf.upfronthosting.co.za>
In-reply-to
Content
> I've added a new patch, that implements a shared/exclusive lock as 
> described in my comments above, for the threading and multiprocessing 
> module.

The patch does not seem to touch the threading mode and does not come with tests.  I doubt the multiprocessing version is actually picklable since self._requirement is a lambda function.

Also it would be best to avoid making multiprocessing.synchronize depend on ctypes.  (See implementation of multiprocessing.Barrier or Issue #14953.)


Personally, I would prefer to make the shared and exclusive locks attributes of the same object, so one could do

   with selock.shared:
      ...

   with selock.exclusive:
      ...
History
Date User Action Args
2012-09-30 14:00:26sbtsetrecipients: + sbt, pitrou, kristjan.jonsson, jyasskin, asvetlov, mklauber, Sebastian.Noack
2012-09-30 14:00:26sbtsetmessageid: <1349013626.57.0.524502900149.issue8800@psf.upfronthosting.co.za>
2012-09-30 14:00:26sbtlinkissue8800 messages
2012-09-30 14:00:26sbtcreate