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 pitrou
Recipients grahamd, ncoghlan, pitrou
Date 2012-08-21.15:51:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1345564090.3326.1.camel@localhost.localdomain>
In-reply-to <>
> If we expose an official way to switch the destination of the
> PyGILState APIs, then what it means is that mod_wsgi can, over the
> lifecycle of a single process in the pool, *switch* the virtual host
> and WSGI endpoint that process is handling by changing the active
> interpreter.

I don't understand what that means. It's the OS which switches threads,
including interpreter threads.

(by the way, the real fix to the GILState vs. subinterpreters issue
would be to create new API functions which take an interpreter as
argument, so that you have a distinct TLS key per interpreter)
Date User Action Args
2012-08-21 15:51:24pitrousetrecipients: + pitrou, ncoghlan, grahamd
2012-08-21 15:51:24pitroulinkissue15751 messages
2012-08-21 15:51:24pitroucreate