If you can manage to get it down to a small example then we can verify it and if need be lodge it as a Python bug report. They may well have missed some corner case.
Graham On 5 December 2012 05:03, Gnarlodious <[email protected]> wrote: > I was able to zero in on the cause of the problem, sort of. I > inadvertently fixed the problem by importing my Gnomon module in my *.wsgi > script, just like with the other two Python modules that errored. I am not > sure what is so special about my Gnomon module that causes the error, > except that in it that I overrode the time module by saying > > import time as Pytime > > This because I need to use "time" as the name of a query string variable > name. This looks like the cause of mod_wsgi's inability to find Pytime. > Importing Gnomon in *.wsgi somehow enables the webapp to know where > Pytime._strptime > is located. Note the underscore before the name, I don't know what the > signficance of that is. In any case, this problem only occurs inside > mod_wsgi. The script runs normally in single-shot mode, and also > interactively. > > This evidently is a feature of Python 3.3.0. Or possibly a bug. > > -- Gnarlie > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/modwsgi/-/s7P3ZMrFghAJ. > > 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. > -- 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.
