From 7bbfc43e34c1909b8edfc8e3188c35447cffef15 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Tue, 17 Nov 2015 10:50:00 -0500 Subject: [PATCH] [1.9.x] Refs #24971, #25356 -- Clarified how apps.py works in 1.9 release notes. Backport of 6258e163352690faf20bfc92c12468316d1a47ae from master --- docs/ref/applications.txt | 2 ++ docs/releases/1.9.txt | 6 +++++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/ref/applications.txt b/docs/ref/applications.txt index 498e10c954..4184398fbb 100644 --- a/docs/ref/applications.txt +++ b/docs/ref/applications.txt @@ -41,6 +41,8 @@ interact with installed applications, mainly for configuration and also for introspection. That's why the application registry maintains metadata in an :class:`~django.apps.AppConfig` instance for each installed application. +.. _configuring-applications-ref: + Configuring applications ======================== diff --git a/docs/releases/1.9.txt b/docs/releases/1.9.txt index d601e36fd4..eda6cf1a80 100644 --- a/docs/releases/1.9.txt +++ b/docs/releases/1.9.txt @@ -428,7 +428,11 @@ Management Commands * The :djadmin:`createcachetable` command now has a ``--dry-run`` flag to print out the SQL rather than execute it. -* The :djadmin:`startapp` command creates an ``apps.py`` file. +* The :djadmin:`startapp` command creates an ``apps.py`` file. Since it doesn't + use ``default_app_config`` (:ref:`a discouraged API + `), you must specify the app config's path, + e.g. ``'polls.apps.PollsConfig'``, in :setting:`INSTALLED_APPS` for it to be + used (instead of just ``'polls'``). * When using the PostgreSQL backend, the :djadmin:`dbshell` command can connect to the database using the password from your settings file (instead of