On Fri, May 23, 2008 at 12:11 PM, David Robinson <[EMAIL PROTECTED]> wrote:
> > I have run into a problem that I don't understand - when I try to run > "shell manage.py shell" I just started getting an error about the > DJANGO_SETTINGS_MODULE environment variable not being defined. > You mean "python manage.py shell", right? > > I found the information I needed to work around the problem (on this > list - thank you, Evert Rol). I added these two lines to manage.py: > > import os > os.environ['DJANGO_SETTINGS_MODULE'] = 'myproject.settings' > > and that took care of it. But it seems very strange that something like > manage.py would stop working. > > I did just switch to the newforms-admin branch, but toggling back to the > Django trunk doesn't fix the problem. We are storing a few working > copies of our code on the same development box so that a few of us can > work on things without getting in each other's way. I don't know if > something connected to that could mess things up. > > I'm sorry for not posing a clear, concise question, but does anyone have > any suggestions about what would keep manage.py from being able to set > that environment variable? > manage.py doesn't set the environment variable, it just imports settings assuming it is in the current directory. Since you don't get an error message that that failed, presumably it worked so the question is why is some subsequent code trying to use the environment variable even though settings has already been loaded. To help answer that question, the full traceback from the error case would be helpful. Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
