Re: [modwsgi] ImportError: No module named threading

2012-10-29 Thread Gnarlodious
It seems to be working now after restarting Apache using: sudo launchctl unload -w /System/Library/LaunchDaemons/org.apache.httpd.plist sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist This restarts the parent process of the Apache instance Server.app uses.

Re: [modwsgi] ImportError: No module named threading

2012-10-29 Thread Gnarlodious
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

Re: [modwsgi] ImportError: No module named threading

2012-10-29 Thread Graham Dumpleton
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 gnarlodi...@gmail.com

Re: [modwsgi] ImportError: No module named threading

2012-10-29 Thread Gnarlodious
The two paths are identical at the *.wsgi script and also at the *.py script that crashes. -- Gnarlie On Monday, October 29, 2012 5:55:02 AM UTC-6, Graham Dumpleton wrote: You aren't playing around with sys.path in the WSGI script file and mucking up what was in it to begin with? Try

Re: [modwsgi] configure not using --exec_prefix

2012-10-29 Thread Hugh McManus
Hey Graham, Thanks for getting back to me on this. Yes you're right, I'm not sure that what I've done is enough. In fact you've pointed out how little I know of configure files and their ecosystem altogether. This is my real first attempt at looking at those types of files and I was only