First time here? Check out the FAQ!

Revision history  [back]

Possibly this will help you http://serverfault.com/questions/285229/python-django-wsgi-apache-importerror-no-module-named-site

It is likely that mod_wsgi was compiled for a different version of python intepreter.

You can verify that by finding the mod_wsgi.so file and typing ldd mod_wsgi.so - you'll see the list of libraries linked to the apache module.

It might be helpful to stick some debugging statements into the wsgi script, for example:

import sys
sys.stderr.write('\n'.join(sys.path))

If you notice that there are paths to an unrelated python version - that would indicate the diagnosys I mentioned.

Possibly this will help you http://serverfault.com/questions/285229/python-django-wsgi-apache-importerror-no-module-named-site

It is likely that mod_wsgi was compiled for a different version of python intepreter.

You can verify that by finding the mod_wsgi.so file and typing ldd mod_wsgi.so - you'll see the list of libraries linked to the apache module.

It might be helpful to stick some debugging statements into the wsgi script, for example:

import sys
sys.stderr.write('\n'.join(sys.path))

If you notice that there are paths to an unrelated python version - that would indicate the diagnosys symptom I mentioned.

Possibly this will help you http://serverfault.com/questions/285229/python-django-wsgi-apache-importerror-no-module-named-site

It is likely that mod_wsgi was compiled for a different version of python intepreter.

You can verify that by finding the mod_wsgi.so file and typing ldd mod_wsgi.so - you'll see the list of libraries linked to the apache module.

It might be helpful to stick some debugging statements into the wsgi script, for example:

import sys
sys.stderr.write('\n'.join(sys.path))

If you notice that there are paths to an unrelated python version - that would indicate the symptom I mentioned.