Message169516
The problem is: threading.Lock raises ThreadingError (which is subclass of RuntimeError for 3.3 but not for 3.2), but threading.Condition raises RuntimeError for the same reason.
RLock behavior is even worse: it raises ThreadingError if C accelerator is available in _thread and RuntimeError otherwise.
I think RuntimeError should be replaced by ThreadingError for _RLock and Condition implementations as well as docs need to be updated.
Also I think this patch should be applied to 3.4 only, it is enchacement, not bugfix.
About fixing docs for 2.7-3.3: I see nothing wrong if current inconsistency will be documented, perhaps as *warning* or *note* block. |
|
Date |
User |
Action |
Args |
2012-08-31 10:22:41 | asvetlov | set | recipients:
+ asvetlov, docs@python, mikehoy |
2012-08-31 10:22:41 | asvetlov | set | messageid: <1346408561.03.0.817304013462.issue15829@psf.upfronthosting.co.za> |
2012-08-31 10:22:40 | asvetlov | link | issue15829 messages |
2012-08-31 10:22:40 | asvetlov | create | |
|