Clarified (hopefully) how to use the default settings override in configure().
git-svn-id: http://code.djangoproject.com/svn/django/trunk@2932 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
eb707d8c43
commit
390231d406
|
@ -771,6 +771,13 @@ is equivalent::
|
|||
|
||||
settings.configure(myapp_defaults, DEBUG = True)
|
||||
|
||||
Normally, you will not need to override the defaults in this fashion. The
|
||||
Django defaults are sufficiently tame that you can safely use them. Be aware
|
||||
that if you do pass in a new default module, it entirely *replaces* the Django
|
||||
defaults, so you must specify a value for every possible setting that might be
|
||||
used in that code you are importing. Check in
|
||||
``django.conf.settings.global_settings`` for the full list.
|
||||
|
||||
Either configure() or DJANGO_SETTINGS_MODULE is required
|
||||
--------------------------------------------------------
|
||||
|
||||
|
|
Loading…
Reference in New Issue