On Thursday, August 5, 2010 11:12:51 PM UTC-4, Graham Dumpleton wrote:
> Try with mod_wsgi 3.3, but add:
>
WSGIApplicationGroup %{GLOBAL}
>
> to force use of main Python interpreter.
>
>
> Graham, thanks so much for this advice. This solved a persistent problem
for me.
Are there downsides to doing this -- should I be motivated to find & solve
the root cause? Or is the WSGIApplicationGroup approach something I can
use in the long term and not worry about?
Is there a way to identify the offending module that's causing the GIL
problem?
Thank you
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/modwsgi?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
