- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message190604
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.
| Author | neologix |
|---|---|
| Recipients | JBernardo, neologix, pitrou, rhettinger, sbt |
| Date | 2013-06-04.16:25:18 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <CAH_1eM2woCLxpR_RJeweyH0kn+4CznkgNTSjVJU_-ke-M82Nsw@mail.gmail.com> |
| In-reply-to | <1370354799.69.0.572004998472.issue18078@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> Which just means that waiting on C conditions is C times more expensive than > waiting on 1 currently is. That seems reasonable enough to me, and anyway, > I would expect C to be fairly small. Waking up a single thread (through notify()) is currently O(1) (since it's unqueued from the head of the deque). Here, removing a thread from a wait queue other than the one from which it was signalled is O(waiting threads). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-06-04 16:25:18 | neologix | set | recipients: + neologix, rhettinger, pitrou, sbt, JBernardo |
| 2013-06-04 16:25:18 | neologix | link | issue18078 messages |
| 2013-06-04 16:25:18 | neologix | create | |

