From ae9f9dc37f39afeaa45c646cf6eef81beffcf021 Mon Sep 17 00:00:00 2001 From: David Sanders Date: Tue, 29 Sep 2015 15:29:59 +1000 Subject: [PATCH] =?UTF-8?q?Improved=20"=E2=80=9Cstandalone=E2=80=9D=20Djan?= =?UTF-8?q?go=20usage"=20example.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/topics/settings.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/topics/settings.txt b/docs/topics/settings.txt index 2d44a84364..55e8d221c3 100644 --- a/docs/topics/settings.txt +++ b/docs/topics/settings.txt @@ -277,13 +277,15 @@ After you've either set :envvar:`DJANGO_SETTINGS_MODULE` or called ``configure()``, you'll need to call :func:`django.setup()` to load your settings and populate Django's application registry. For example:: + import django from django.conf import settings from myapp import myapp_defaults settings.configure(default_settings=myapp_defaults, DEBUG=True) django.setup() - # Now this script can use any part of Django it needs. + # Now this script or any imported module can use any part of Django it needs. + from myapp import models Note that calling ``django.setup()`` is only necessary if your code is truly standalone. When invoked by your Web server, or through :doc:`django-admin