Author ncoghlan
Recipients amaury.forgeotdarc, grahamd, loewis, ncoghlan, pitrou
Date 2011-01-15.23:41:28
SpamBayes Score 7.75799e-09
Marked as misclassified No
Message-id <1295134891.43.0.141462766065.issue10915@psf.upfronthosting.co.za>
In-reply-to
Content
A TLS based approach would presumably allow an embedding application like mod_wsgi to tinker with the state of threads created by naive modules that are unaware of the existence of subinterpreters.

That said, I don't see anything that prevents us from pursuing a TLS based override for the existing PyGILState functions later if the simpler, more explicit approach proves inadequate. As it stands, the new explicit calls allow something like mod_wsgi to define its *own* TLS location for the interpreter that is currently handling callbacks into Python, then use SWIG to generate PyGILState_*Ex calls in callback wrappers that reference that TLS interpreter state.
History
Date User Action Args
2011-01-15 23:41:31ncoghlansetrecipients: + ncoghlan, loewis, amaury.forgeotdarc, pitrou, grahamd
2011-01-15 23:41:31ncoghlansetmessageid: <1295134891.43.0.141462766065.issue10915@psf.upfronthosting.co.za>
2011-01-15 23:41:28ncoghlanlinkissue10915 messages
2011-01-15 23:41:28ncoghlancreate