Browse files

Fix issue #18267 - document `settings.configured` property.

  • Loading branch information...
techtonik committed May 3, 2012
1 parent 00c0d3c commit 59d2b8aa16126d8d0a453f07d5c3497048bcd6b0
Showing with 11 additions and 2 deletions.
  1. +11 −2 docs/topics/settings.txt
@@ -220,7 +220,7 @@ In this example, default settings are taken from ``myapp_defaults``, and the
The following example, which uses ``myapp_defaults`` as a positional argument,
is equivalent::
- settings.configure(myapp_defaults, DEBUG = True)
+ 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
@@ -242,7 +242,16 @@ is accessed.
If you set ``DJANGO_SETTINGS_MODULE``, access settings values somehow, *then*
call ``configure()``, Django will raise a ``RuntimeError`` indicating
-that settings have already been configured.
+that settings have already been configured. There is a property just for this
+.. attribute: django.conf.settings.configured
+For example::
+ from django.conf import settings
+ if not settings.configured:
+ settings.configure(myapp_defaults, DEBUG=True)
Also, it's an error to call ``configure()`` more than once, or to call
``configure()`` after any setting has been accessed.

0 comments on commit 59d2b8a

Please sign in to comment.