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 | pitrou |
|---|---|
| Recipients | kristjan.jonsson, loewis, paul.moore, pitrou, python-dev, sbt, vstinner |
| Date | 2012年06月19日.13:51:41 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1340113902.29.0.264454663931.issue15038@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> However, if this lost wakeup problem can affect current users of the API, then it sounds unacceptable. Let me elaborate: the GIL can perhaps suffer lost wakeups from time to time. The Lock API certainly shouldn't. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012年06月19日 13:51:42 | pitrou | set | recipients: + pitrou, loewis, paul.moore, kristjan.jonsson, vstinner, python-dev, sbt |
| 2012年06月19日 13:51:42 | pitrou | set | messageid: <1340113902.29.0.264454663931.issue15038@psf.upfronthosting.co.za> |
| 2012年06月19日 13:51:41 | pitrou | link | issue15038 messages |
| 2012年06月19日 13:51:41 | pitrou | create | |