On Wed, 2006-08-09 at 12:54 -0700, plungerman wrote: > dude, that was it. i was importing the module with from myapp import > my_settings and not doing a relative import as you suggested from > settings_default import *
To provide some background information, here is the way we process settings (and why the ".. import *' bit is necessary). To avoid having to read the developer's mind, the settings stuff is reasonably simple (it's partly for your own protection, too)... When it comes time to instantiate a settings object, the code reads through the settings module (either the thing referred to by DJANGO_SETTINGS_MODULE or the default object passed into settings.configure()) and extracts every variable that is in all-upper-case (anything where varname == varname.upper() in Python code). So you need to import your settings_default variables into the namespace of the "real" settings module, rather than leaving them in the settings_default namespace. It also means that if you want to create any new settings of your own, they should be in all upper-case (underscores and digits are permitted, too). Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
