Message157544
From docs@python.org:
"""
I recently ran into a situation where I could not be certain that a lock
was currently in the acquired state. I checked the documentation to
determine what would happen if I attempted to release a lock that was
already released, and saw an ominous warning of "Do not call this method
when the lock is unlocked."
Needing to know what would happen, I cautiously tested it out. I half
expected my computer to explode as I released a lock for the second
time, but was pleased to see it raise a 'thread.error' exception which
could be caught and handled.
I generally expect the documentation to tell me what will happen if I do
something invalid. In this case the documentation should indicate that a
thread.error will be raised if you release an unlocked lock.
"""
I agree: if we know that a ThreadError will always be raised in this instance, we should document it as such. |
|
Date |
User |
Action |
Args |
2012-04-05 07:06:56 | georg.brandl | set | recipients:
+ georg.brandl, pitrou, docs@python |
2012-04-05 07:06:56 | georg.brandl | set | messageid: <1333609616.9.0.633115743228.issue14502@psf.upfronthosting.co.za> |
2012-04-05 07:06:56 | georg.brandl | link | issue14502 messages |
2012-04-05 07:06:55 | georg.brandl | create | |
|