Message183869
Tim, do you remember why Condition.notify() went to great lengths to act as if the lock could be released after the check for self._is_owned()?
It loops over its own a copy of __waiters, and the __waiters.remove(waiter) code is wrapped in a try/except to detect a situation where __waiters mutated during the release-loop. I'm presuming that defensive programming was put there for a reason. |
|
Date |
User |
Action |
Args |
2013-03-10 06:35:45 | rhettinger | set | recipients:
+ rhettinger, tim.peters, jcea, pitrou, neologix |
2013-03-10 06:35:45 | rhettinger | set | messageid: <1362897345.56.0.951698048186.issue17385@psf.upfronthosting.co.za> |
2013-03-10 06:35:45 | rhettinger | link | issue17385 messages |
2013-03-10 06:35:45 | rhettinger | create | |
|