Hi Graham, Thanks so much for your help before, and for the continued development of mod_wsgi - it's such linchpin product in many site. I'm astounded by your efforts esp. as you say you don't run it yourself.
I've a slightly cooked up scenario where I've compiled mod_wsgi with a custom (enthought) python distribution. I have had to use patchelf to get mod_wsgi.so to search the correct library paths to find libpython.so. This doesn't seem to be a big issue as things work - see below. I would like mod_wsgi to source a virtualenv python clone of the epd python. This works absolutely wonderfully if I set PYTHONHOME=/path/to/ virtualenv in a terminal and start apache from that terminal. But - (as you may guess) when I try to get this to run daemonized (ie with $ service httpd restart - or whatever as if the system was booting) then this fails. I set either (or both) of WSGIPythonHome /path/to/virtualenv SetEnv PYTHONHOME /path/to/virtualenv in httpd.conf and I get the following information messages from error.log [Thu May 26 18:53:26 2011] [info] mod_wsgi (pid=19324): Python home / path/to/virtualenv. [Thu May 26 18:53:26 2011] [info] mod_wsgi (pid=19324): Initializing Python. Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>] ImportError: No module named site Of course, setting $PYTHONHOME works - but I can't set $PYTHONHOME from during boot (or simple daemon restart) or can I? Does this sound familiar and could you help? I have tried (and appreciated) your thorough documentation but find myself stuck on this. Many thanks, Dan -- 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.
