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 | fdirosa |
|---|---|
| Recipients | fdirosa, nnorwitz, timbishop, vslavik |
| Date | 2008年05月28日.16:55:21 |
| SpamBayes Score | 0.090519324 |
| Marked as misclassified | No |
| Message-id | <1211993723.54.0.399659700613.issue1758146@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The documentation states that thread states are supported within a single interpreter and not supported across other interpreters (specifically for the GIL functions which are just wrapper functions around the PyEval_ functions). So I would have to conclude then that the condition should check to see if the swapping thread is within the current interpreter state otherwise "fatal error", as such... The condition: check->interp == newts->interp should be: check->interp != newts->interp In otherwords if there is a previous thread state and it's interpreter is NOT the same as the one being swapped in then do the fatal error. Just my opinion. I ran into this problem when using the PyThreadState_Swap function directly (low level) to do the thread handling within a single interpreter state (Debug mode only). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年05月28日 16:55:23 | fdirosa | set | spambayes_score: 0.0905193 -> 0.090519324 recipients: + fdirosa, nnorwitz, timbishop, vslavik |
| 2008年05月28日 16:55:23 | fdirosa | set | spambayes_score: 0.0905193 -> 0.0905193 messageid: <1211993723.54.0.399659700613.issue1758146@psf.upfronthosting.co.za> |
| 2008年05月28日 16:55:22 | fdirosa | link | issue1758146 messages |
| 2008年05月28日 16:55:22 | fdirosa | create | |