Hi, I am just starting to move from mod_python to mod_wsgi and am also setting up virtualenvs for my projects (several running from one apache server)
I set up a virgin virtual env to use as the base env - each site will then have it's own virtualenv I have put this into my httpd.conf file WSGIPythonHome /usr/local/pythonenv/BASELINE But it doesn't seem to have any effect - I am getting an django import error that's coming from my server wide python directory: [Wed Oct 05 21:41:41 2011] [error] [client 80.119.239.216] File "/ usr/local/lib/python2.5/site-packages/django/core/handlers/base.py", line 42, in load_middleware [Wed Oct 05 21:41:41 2011] [error] [client 80.119.239.216] raise exceptions.ImproperlyConfigured, 'Error importing middleware %s: "%s"' % (mw_module, e) [Wed Oct 05 21:41:41 2011] [error] [client 80.119.239.216] ImproperlyConfigured: Error importing middleware django.middleware.csrf: "No module named csrf" This error is because I need to use Django1.3 on the site causing the error - I know that, but the file causing it is from my server wide python install - not from any virtualenv? I am expecting an import error because I've not even setup any versions of Django yet! Why might Apache / mod_wsgi be ignoring the PythonHome directive? how could I find out further? I don't get any errors on an apache restart.. Thanks, Guy -- 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.
