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, fdirosa, nnorwitz, timbishop, vslavik
Date 2008-07-09.05:26:00
SpamBayes Score 0.040749073
Marked as misclassified No
Message-id <1215581164.42.0.0500202614042.issue1758146@psf.upfronthosting.co.za>
In-reply-to
Content
It's only checking that the original tstate *for the current thread* and
the new tstate have a different subinterpreter.  A subinterpreter can
have multiple tstates, so long as they're all in different threads.

The documentation is referring specifically to the PyGILState_Ensure and
PyGILState_Release functions.  Calling these says "I want a tstate, and
I don't know if I had one already".  The problem is that, with
subinterpreters, you may not get a tstate with the subinterpreter you
want.  subinterpreter references saved in globals may lead to obscure
crashes or other errors - some of these have been fixed over the years,
but I doubt they all have.
History
Date User Action Args
2008-07-09 05:26:04Rhamphoryncussetspambayes_score: 0.0407491 -> 0.040749073
recipients: + Rhamphoryncus, nnorwitz, timbishop, vslavik, fdirosa
2008-07-09 05:26:04Rhamphoryncussetspambayes_score: 0.0407491 -> 0.0407491
messageid: <1215581164.42.0.0500202614042.issue1758146@psf.upfronthosting.co.za>
2008-07-09 05:26:03Rhamphoryncuslinkissue1758146 messages
2008-07-09 05:26:01Rhamphoryncuscreate