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 | grahamd |
|---|---|
| Recipients | Rhamphoryncus, fdirosa, grahamd, nnorwitz, timbishop, vslavik |
| Date | 2008年07月24日.15:11:55 |
| SpamBayes Score | 4.9972795e-07 |
| Marked as misclassified | No |
| Message-id | <1216912317.57.0.32356859179.issue1758146@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I do understand. The initial thread, which is effectively a foreign thread to Python to begin with, when used to initialise Python, ie., call Py_Initialize(), is treated in a special way in as much as as a side effect it does that initialisation of GIL internal thread state. This is as you say. But, this is the only foreign thread this implicitly occurs for and why the main thread is a bit special. If you were to create additional foreign threads outside of Python, ie., in addition to main thread which initialised it, those later threads should not fail the Py_DEBUG test unless the code they execute explicitly calls the simplified API and by doing so implicitly causes internal threadstate for that thread to be created. Hope this makes sense. Sorry, in a bit of a hurry. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月24日 15:11:57 | grahamd | set | spambayes_score: 4.99728e-07 -> 4.9972795e-07 recipients: + grahamd, nnorwitz, Rhamphoryncus, timbishop, vslavik, fdirosa |
| 2008年07月24日 15:11:57 | grahamd | set | spambayes_score: 4.99728e-07 -> 4.99728e-07 messageid: <1216912317.57.0.32356859179.issue1758146@psf.upfronthosting.co.za> |
| 2008年07月24日 15:11:56 | grahamd | link | issue1758146 messages |
| 2008年07月24日 15:11:55 | grahamd | create | |