This is why, eventhough its noted in the docs as optional, I add the pythonpath to my site in the apache vhosts file by default. Adding the path globally isn't really a good thing to do but adding it whenever your webserver starts the site its needed for, even if its already defined somewhere else, is imho a good practice.
On Aug 28, 5:49 pm, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote: > On 8/28/07, Rob Hudson <[EMAIL PROTECTED]> wrote: > > > Has anyone else noticed this? Isn't "./manage.py" supposed to set up > > the settings module correctly? > > manage.py just tries to import the settings module directly; it > basically assumes that '.' is on your sys.path, that "settings" is the > name of your settings module, and that the current working directory > contains the settings module. > > Is it possible any of those things changed? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
