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 | amaury.forgeotdarc |
|---|---|
| Recipients | Rhamphoryncus, amaury.forgeotdarc, gregory.p.smith, gvanrossum |
| Date | 2008年01月17日.22:39:19 |
| SpamBayes Score | 0.0069954274 |
| Marked as misclassified | No |
| Message-id | <1200609562.44.0.212428579795.issue1856@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> PyGILState_Ensure would still be broken. > It touches various things that get torn down (autoInterpreterState, > autoTLSkey, and the HEAD_LOCK macros) before it grabs the GIL. > Reordering should be possible of course. Adam, did you notice the change on revision 59231 ? the PyGILState_Ensure stuff should now remain valid during the PyInterpreterState_Clear() call. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年01月17日 22:39:22 | amaury.forgeotdarc | set | spambayes_score: 0.00699543 -> 0.0069954274 recipients: + amaury.forgeotdarc, gvanrossum, gregory.p.smith, Rhamphoryncus |
| 2008年01月17日 22:39:22 | amaury.forgeotdarc | set | spambayes_score: 0.00699543 -> 0.00699543 messageid: <1200609562.44.0.212428579795.issue1856@psf.upfronthosting.co.za> |
| 2008年01月17日 22:39:20 | amaury.forgeotdarc | link | issue1856 messages |
| 2008年01月17日 22:39:19 | amaury.forgeotdarc | create | |