Henrik, I've been stuck in a a place like Ron's all morning. I thought I had gotten to a later problem when I started getting Django errors indication that there was 'no module mysite.urls', but I just gave it another try, and I'm back to the mod-python error 'no module named mysite'. I seem to be at a point where I get to choose between the mod-python and Django errors about non-existence of modules. At least I no longer have Apache 'no such place' errors.
Do you know why there is such a lag in response to configuration file changes? When I change httpd.conf and restart Apache, it seems to see new settings fairly quickly, but when I change settings.py, Django does not "catch up" for quite a while. I tried deleting everything I could find with a .pyc extension, but that does not seem to help, (and may be causing some actual harm?) I have gotten the full tutorial to work (WinXP, Python 2.4.1/mod- python3.2.8 /Django 0.95) with the development web server, and the next place to go is Apache (2.0.59, at least for now). I intend to move to Linux, but for reasons of practicality I am currently working in Windows. Thanks for any light you can shed on this. John. On Feb 1, 7:09 am, "HenrikG" <[EMAIL PROTECTED]> wrote: > Hi Ron! > > Try changing > '/home/rsie/projects/mysite' > to > '/home/rsie/projects' > > and also change > SetEnv DJANGO_SETTINGS_MODULE settings > to > SetEnv DJANGO_SETTINGS_MODULE mysite.settings > > regards, > /Henrik --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
