I am using mod_wsgi 2.3 in daemon mode, Apache and virtualenv 1.3.3. I have a default Django install in my system site-packages but my virtualenvs are being made with --no-site-packages. My other sites have been working fine because I have been using Django 1.0 and that's the same one in my system site-packages. I just made a new Django app that uses 1.1 and noticed a problem. It seems that the system Django 1.0 is on my pythonpath and when the wsgi gets ran it is trying to use the system Django 1.0.
I looked through several posts and various information on the mod_wsgi site while trying several things to fix this. However nothing has worked so far. I was wondering if someone here may be able to help? Here is the wsgi file. I tried to reconfigure the pythonpath so the virtualenv's site-packages is first. It seems like they are being reordered but the site just hangs when I try to access it. If I used the old file it would always say there is a problem in the admin urls because it was trying to access the system's Django 1.0. http://dpaste.com/136073/ Here is my httpd.conf http://dpaste.com/136075/ I don't know if this is related or not but the Apache error.log is showing this on startup... http://dpaste.com/136078/ The above error message is using the correct version of Django. Thanks in advance for any help you may be able to provide. I changed the instances of my username and the site being used. -- 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.
