Dear Graham First, I want to thank you for your quick support (even on weekends!)!
As you suggested I made a fresh compile & install of mod_wsgi with the "--with-python" option. Doing so I got rid of the apache warnings. Unfortunately though, it still uses the wrong Python path ( /usr/ lib/... ) - I realised that when getting the same module-import-error in the wsgi-script as before. (The directory to the module IS on the /opt/python2.5/... python path) I tried to set WSGIPythonPath to my module in the apache configuration file - without success. Do you have one more suggestion? Kind regards, Lukas PS: It is weird, starting python from the console and importing the module works like a charm... PPS: The module-import-error from the apache error.log: File "/var/www/wsgi-scripts/myapp.wsgi", line 8, in <module> import django.core.handlers.wsgi ImportError: No module named django.core.handlers.wsgi --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
