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 steinn
Recipients steinn
Date 2014-04-24.06:00:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398319251.34.0.871128764935.issue21342@psf.upfronthosting.co.za>
In-reply-to
Content
In the documentation of multiprocessing the locks, RLock and Lock, 
are said to be clones of their respective threading synchronization primitives.

There is an inconsistency in what exceptions are raised when an
unlocked lock is released. According to the threading documentation a 
RuntimeError should be raised.

Lock.release raises ValueError 
RLock.release raises AssertionError

Tested this in python 2.7, 3.2, 3.4, 3.5 and broken in all those versions.

The attached patch fixes this for 3.5
History
Date User Action Args
2014-04-24 06:00:51steinnsetrecipients: + steinn
2014-04-24 06:00:51steinnsetmessageid: <1398319251.34.0.871128764935.issue21342@psf.upfronthosting.co.za>
2014-04-24 06:00:51steinnlinkissue21342 messages
2014-04-24 06:00:50steinncreate