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 ncoghlan
Recipients grahamd, ncoghlan, pitrou
Date 2012-08-21.15:23:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
s/slightly/completely/ (I believe my description of the core problem was right, but my description of why that problem exists was wrong - it actually has to do with the way mod_wsgi handles virtual hosts and endpoints)

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. There are still some extension modules where that won't work (because they create persistent threads that periodically call back into Python, so they may still end up calling back in to the wrong interpreter), but it will allow those that just do callbacks from external worker threads (or other operations that are similarly bound by the lifecycle of a request) to start working properly.
Date User Action Args
2012-08-21 15:23:57ncoghlansetrecipients: + ncoghlan, pitrou, grahamd
2012-08-21 15:23:56ncoghlansetmessageid: <>
2012-08-21 15:23:56ncoghlanlinkissue15751 messages
2012-08-21 15:23:55ncoghlancreate