➜

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 petri.lehtinen
Recipients Jim.Jewett, docs@python, georg.brandl, petri.lehtinen, pitrou, python-dev, r.david.murray, sandro.tosi, vinay.sajip
Date 2012-06-06.18:00:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1339005657.14.0.652294196637.issue14502@psf.upfronthosting.co.za>
In-reply-to
Content 
The docs of 2.7 and 3.2 still first say that RuntimeError is raised, and then that a ThreadError is raised:

    ...
    If an attempt is made to release an unlocked lock, a RuntimeError
    will be raised.

    ...

Lock.release()
    ...
    When invoked on an unlocked lock, a ThreadError is raised.


In 2.7 and 3.2, ThreadError is not a RuntimeError, so this is wrong.
History
Date User Action Args
2012-06-06 18:00:57petri.lehtinensetrecipients: + petri.lehtinen, georg.brandl, vinay.sajip, pitrou, r.david.murray, sandro.tosi, docs@python, python-dev, Jim.Jewett
2012-06-06 18:00:57petri.lehtinensetmessageid: <1339005657.14.0.652294196637.issue14502@psf.upfronthosting.co.za>
2012-06-06 18:00:51petri.lehtinenlinkissue14502 messages
2012-06-06 18:00:51petri.lehtinencreate