From 390231d4068a550ef8188807c6e7e7b2f0fb1521 Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Wed, 17 May 2006 06:57:22 +0000 Subject: [PATCH] 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 --- docs/settings.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/settings.txt b/docs/settings.txt index f027d5596b..766f26edbb 100644 --- a/docs/settings.txt +++ b/docs/settings.txt @@ -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 --------------------------------------------------------