From 76bf4bc1117524eb1305395451455b372e518c91 Mon Sep 17 00:00:00 2001 From: Aymeric Augustin Date: Mon, 21 Sep 2015 22:42:35 +0200 Subject: [PATCH] [1.8.x] Recommended against default_app_config. Most likely this is a losing fight -- people seem to love this small convention -- but at least the reasons for avoiding it will be documented. Refs #25356. Backport of 94a36cf from master --- docs/ref/applications.txt | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/ref/applications.txt b/docs/ref/applications.txt index 4870e74577..a51b918e66 100644 --- a/docs/ref/applications.txt +++ b/docs/ref/applications.txt @@ -59,6 +59,14 @@ subclass for that application. If there is no ``default_app_config``, Django uses the base :class:`~django.apps.AppConfig` class. +``default_app_config`` allows applications that predate Django 1.7 such as +``django.contrib.admin`` to opt-in to :class:`~django.apps.AppConfig` features +without requiring users to update their :setting:`INSTALLED_APPS`. + +New applications should avoid ``default_app_config``. Instead they should +require the dotted path to the appropriate :class:`~django.apps.AppConfig` +subclass to be configured explicitly in :setting:`INSTALLED_APPS`. + For application authors -----------------------