mirror of
https://github.com/django/django.git
synced 2025-06-16 08:59:17 +00:00
[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
This commit is contained in:
parent
528c1330f8
commit
76bf4bc111
@ -59,6 +59,14 @@ subclass for that application.
|
|||||||
If there is no ``default_app_config``, Django uses the base
|
If there is no ``default_app_config``, Django uses the base
|
||||||
:class:`~django.apps.AppConfig` class.
|
: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
|
For application authors
|
||||||
-----------------------
|
-----------------------
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user