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月17日.22:35:34 |
| SpamBayes Score | 0.029300902 |
| Marked as misclassified | No |
| Message-id | <1200609336.15.0.105322116384.issue1856@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I'm not sure I understand you, Gregory. Are arguing in favour of adding extra logic to the GIL code, or against it? I'm attaching a patch that has non-main thread exit, and it seems to fix the test case. It doesn't fix the PyGILState_Ensure problems though. Also note that PyThread_exit_thread() was completely broken, becoming a no-op once threading was initialized, and even before then it would exit the process rather than just the thread. I've fixed it for pthreads, but not for any of the other platforms. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年01月17日 22:35:36 | Rhamphoryncus | set | spambayes_score: 0.0293009 -> 0.029300902 recipients: + Rhamphoryncus, gvanrossum, gregory.p.smith, amaury.forgeotdarc |
| 2008年01月17日 22:35:36 | Rhamphoryncus | set | spambayes_score: 0.0293009 -> 0.0293009 messageid: <1200609336.15.0.105322116384.issue1856@psf.upfronthosting.co.za> |
| 2008年01月17日 22:35:35 | Rhamphoryncus | link | issue1856 messages |
| 2008年01月17日 22:35:35 | Rhamphoryncus | create | |