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.
Created on 2012年06月06日 10:40 by petri.lehtinen, last changed 2022年04月11日 14:57 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg162401 - (view) | Author: Petri Lehtinen (petri.lehtinen) * (Python committer) | Date: 2012年06月06日 10:40 | |
In the description of section 16.2.2. Lock objects: If an attempt is made to release an unlocked lock, a RuntimeError will be raised. In the description of Lock.release(): When invoked on an unlocked lock, a ThreadError is raised. Apparently, ThreadError is the correct exception. |
|||
| msg162409 - (view) | Author: R. David Murray (r.david.murray) * (Python committer) | Date: 2012年06月06日 13:14 | |
There's already an issue for this (issue 14502), which is closed. If the docs are still wrong you should probably reopen that one, since it has discussion of the issues involved. (Note, however, that ThreadError is RuntimeError, so technically the docs are not *in*correct :) |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022年04月11日 14:57:31 | admin | set | github: 59222 |
| 2012年06月06日 13:14:50 | r.david.murray | set | status: open -> closed superseder: Document better what happens on releasing an unacquired lock nosy: + r.david.murray messages: + msg162409 resolution: duplicate stage: resolved |
| 2012年06月06日 10:40:36 | petri.lehtinen | set | versions: + Python 3.2, Python 3.3 |
| 2012年06月06日 10:40:12 | petri.lehtinen | create | |