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 | Rhamphoryncus |
|---|---|
| Recipients | Rhamphoryncus, amaury.forgeotdarc, gregory.p.smith, gvanrossum |
| Date | 2008年01月18日.00:12:27 |
| SpamBayes Score | 0.0074133305 |
| Marked as misclassified | No |
| Message-id | <1200615148.3.0.935031242749.issue1856@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Hrm. It seems you're right. Python needs thread-local data to determine if the GIL is held by the current thread. Thus, autoTLSkey and all that need to never be torn down. (The check could be done much more directly than the current PyThreadState_IsCurrent machinations, but I digress.) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年01月18日 00:12:28 | Rhamphoryncus | set | spambayes_score: 0.00741333 -> 0.0074133305 recipients: + Rhamphoryncus, gvanrossum, gregory.p.smith, amaury.forgeotdarc |
| 2008年01月18日 00:12:28 | Rhamphoryncus | set | spambayes_score: 0.00741333 -> 0.00741333 messageid: <1200615148.3.0.935031242749.issue1856@psf.upfronthosting.co.za> |
| 2008年01月18日 00:12:27 | Rhamphoryncus | link | issue1856 messages |
| 2008年01月18日 00:12:27 | Rhamphoryncus | create | |