You aren't playing around with sys.path in the WSGI script file and mucking up what was in it to begin with?
Try adding in debug which prints out sys.path in WSGI script file and then later where import of threading was failing. Graham On 29 October 2012 22:50, Gnarlodious <[email protected]> wrote: > OK here is the final report. "import threading" MUST be declared in your > *.wsgi script. If not, you get an error "ImportError: No module named > threading" from any module importing threading. I don't know why this is the > case because it was determined by trial and error. > > Anything else I said about this problem was irrelevant. > > -- Gnarlie > http://Gnarlodious.com > > -- > 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/-/ZMiikafI2yQJ. > > 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.
