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.14:10:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1345558024.3383.3.camel@localhost.localdomain>
In-reply-to <>
> Just as they do today, all externally created threads will still go to
> *one* interpreter when they hit PyGILState_Ensure(). It's just that
> interpreter won't be the main one.

Uh but how does it solve the issue? (unless you create a mod_wsgi app
with only a single worker thread)
Date User Action Args
2012-08-21 14:10:23pitrousetrecipients: + pitrou, ncoghlan, grahamd
2012-08-21 14:10:23pitroulinkissue15751 messages
2012-08-21 14:10:22pitroucreate