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-08.22:25:25
SpamBayes Score 0.00054593856
Marked as misclassified No
Message-id <1215555927.81.0.721762299086.issue1758146@psf.upfronthosting.co.za>
In-reply-to
Content
Franco, you need to look at the line above that check:

	PyThreadState *check = PyGILState_GetThisThreadState();
	if (check && check->interp == newts->interp && check != newts)
		Py_FatalError("Invalid thread state for this thread");

PyGILState_GetThisThreadState returns the original tstate *for that
thread*.  What it's asserting is that, if there's a second tstate *in
that thread*, it must be in a different subinterpreter.

It doesn't prevent your second and third tstate from sharing the same
subinterpreter, but it probably should, as this check implies it's an
invariant.
History
Date User Action Args
2008-07-08 22:25:28Rhamphoryncussetspambayes_score: 0.000545939 -> 0.00054593856
recipients: + Rhamphoryncus, nnorwitz, timbishop, vslavik, fdirosa
2008-07-08 22:25:27Rhamphoryncussetspambayes_score: 0.000545939 -> 0.000545939
messageid: <1215555927.81.0.721762299086.issue1758146@psf.upfronthosting.co.za>
2008-07-08 22:25:27Rhamphoryncuslinkissue1758146 messages
2008-07-08 22:25:26Rhamphoryncuscreate