Message 237085 - Python tracker

➜

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	davin
Recipients	davin, neologix, r.david.murray, sbt, steinn
Date	2015-03-02.21:03:46
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1425330226.92.0.589879888181.issue21342@psf.upfronthosting.co.za>
In-reply-to

Content
The discussion in issue23484 is leading to a recommendation that the docs be changed to reflect the actual behavior of multiprocessing's Lock and its close relatives. As far back as 2.6.9, calling release() on an unlocked threading.Lock triggered a thread.error Exception whereas doing the same on multiprocessing.Lock triggered a ValueError. This discrepancy in the behavior of Lock between modules turns out to not be a recent development. If issue23484 moves forward with changing the documentation to reflect reality, this issue would be addressed as well.

The discussion in issue23484 is leading to a recommendation that the docs be changed to reflect the actual behavior of multiprocessing's Lock and its close relatives.

As far back as 2.6.9, calling release() on an unlocked threading.Lock triggered a thread.error Exception whereas doing the same on multiprocessing.Lock triggered a ValueError.  This discrepancy in the behavior of Lock between modules turns out to not be a recent development.

If issue23484 moves forward with changing the documentation to reflect reality, this issue would be addressed as well.

History
Date	User	Action	Args
2015-03-02 21:03:47	davin	set	recipients: + davin, r.david.murray, neologix, sbt, steinn
2015-03-02 21:03:46	davin	set	messageid: <1425330226.92.0.589879888181.issue21342@psf.upfronthosting.co.za>
2015-03-02 21:03:46	davin	link	issue21342 messages
2015-03-02 21:03:46	davin	create