Try changing: PythonPath "['/root/mysite'] + sys.path"
to PythonPath "['/root'] + sys.path" I think you only need to tell the server where to find 'mysite' since that is the root of your project. mod_python can then resolve 'mysite.settings' because it found mysite in 'root'. Hope this makes sense. Anyway, your problem sounds exactly like what I ran into the first time I moved my project over to mod_python / Apache. Good luck, MelechRic Haku wrote: > Ok, i'm here with another question :D > > Everithing is fine on my development server (windows), but now i want > to put my project on my production server > > My production Server is a VPS running everithing django needs to run, > so i've modified my httpd.conf file adding the following lines: > > <location "/mysite/"> > SetHandler python-program > PythonPath "['/root/mysite'] + sys.path" > PythonHandler django.core.handlers.modpython > SetEnv DJANGO_SETTINGS_MODULE mysite.settings > PythonDebug On > </location> > > but as i restart apache and surf to http://urltoproducion/mysite/ I > always get this ugly page with this ugly error: > > EnvironmentError: Could not import settings 'mysite.settings' (Is it > on sys.path? Does it have syntax errors?): No module named > mysite.settings > > where am i wrong? I guess it's a path problem or something like > that... > > Thank you!!! > > Haku > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
