➜
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 2018-06-12 05:47 by lev.maximov, last changed 2022-04-11 14:59 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg319365 - (view) | Author: Lev Maximov (lev.maximov) * | Date: 2018-06-12 05:47 | |
In `Condition.wait()` the `waiter` lock gets acquired twice, but is released only once (both in timeout and no timeout cases). Is it intentional? |
|||
| msg319647 - (view) | Author: Antoine Pitrou (pitrou) *  |
Date: 2018-06-15 19:00 | |
The `waiter` lock is always removed from `self._waiters` at the end of wait() (either by notify() or by wait() itself), so there's no point in releasing it a second time before destruction. I'm closing this as it's not a bug. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:01 | admin | set | github: 78022 |
| 2018-06-15 19:00:13 | pitrou | set | status: open -> closed nosy: + pitrou, tim.peters messages: + msg319647 resolution: not a bug stage: resolved |
| 2018-06-12 05:47:47 | lev.maximov | create | |