Author pitrou
Recipients amaury.forgeotdarc, grahamd, loewis, pitrou
Date 2011-01-15.14:52:39
SpamBayes Score 4.9763e-05
Marked as misclassified No
Message-id <1295103161.75.0.771875465176.issue10915@psf.upfronthosting.co.za>
In-reply-to
Content
It should be relatively easy to devise a new PyGILState API with support for multiple interpreters. We just need two new functions (similar to the two existing ones) taking a PyInterpreterState* parameter; a TLS key can be added to the PyInterpreterState structure (instead of the current global TLS key).

It will be up to the caller to know which interpreter they want to hook into when calling these functions (which is application-dependent and is normally well-defined, e.g. when calling a Python callback, you should call it with the interpreter which was in use when registering the callback (i.e. ``PyThreadState_Get()->interp``)).
History
Date User Action Args
2011-01-15 14:52:41pitrousetrecipients: + pitrou, loewis, amaury.forgeotdarc, grahamd
2011-01-15 14:52:41pitrousetmessageid: <1295103161.75.0.771875465176.issue10915@psf.upfronthosting.co.za>
2011-01-15 14:52:39pitroulinkissue10915 messages
2011-01-15 14:52:39pitroucreate