Message168815
| Author |
pitrou |
| Recipients |
grahamd, ncoghlan, pitrou |
| Date |
2012年08月21日.22:31:52 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1345588102.3326.21.camel@localhost.localdomain> |
| In-reply-to |
<1345587272.98.0.214034944684.issue15751@psf.upfronthosting.co.za> |
| Content |
Le mardi 21 août 2012 à 22:14 +0000, Graham Dumpleton a écrit :
> Any third party module then which uses the simplistic calling sequence
> of calling PyGILState_Release() on exiting Python code and thence
> within the same thread calling PyGILState_Ensure() when coming back
> into Python with a callback will work, as mod_wsgi has specified the
> interpreter context for that thread at that time.
Why would a module do that, instead of using
Py_{BEGIN,END}_ALLOW_THREADS? |
|