It did not even try to import them. You can see the sys.modules state of
the WSGI script in my previous response
<https://groups.google.com/group/modwsgi/msg/b962ba2ee7d90709> (no
"encodings" and "codecs" modules imported) and I also verified that with
file-write debugging in the "encodings" module - it really does not get
loaded in the subinterpreters.

On 16.03.2011 16:37, Joonas Lehtolahti wrote:
> [cut out the long post]
>
> Interesting, it seems like there really happens a difference between
> initialization of sub-interpreters to the main one. But was there no
> errors importing encodings in the sub-interpreters either, or did it
> not even try to import the encodings package at all?
>
> For the record, I have all the encodings and stuff in all my Python
> sub-interpreters and none of my pages are using global application
> group, so it is not a generic problem that happens for everyone; just
> like with EventScripts (the other project embedding Python I mentioned
> earlier) it works fine for most people but fails to include the codecs
> for some people.
>
> It's too bad the error doesn't happen to me. If it did, I would surely
> dig as deep as would be needed (even to edit Python's source code to
> add additional debug messages) to find out what exactly causes it. I
> don't know the internal structure of Python enough to be able to
> provide such edits for remote debugging, though. But this is certainly
> an interesting problem and not just mod_wsgi specific. If we can find
> out the cause and solution for it, that would help not only your case
> but also plenty of people using other embedded Python interpreters.
> (You might see that my motivation for actively trying to participate
> in this particular problem is mostly because of the similar problem in
> ES and there is a major pain that has been reported to happen to more
> than just one user)
>

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/modwsgi?hl=en.

Reply via email to