Fixed #21018 -- Reversed precedence order for management commands.

2 files changed, 16 insertions, 0 deletions

diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt
index 62e7920c01..4181d152ef 100644
--- a/docs/ref/settings.txt
+++ b/docs/ref/settings.txt
@@ -1319,6 +1319,10 @@ Django installation. Each string should be a dotted Python path to:
     These rules apply regardless of whether :setting:`INSTALLED_APPS`
     references application configuration classes on application packages.
 
+When several applications provide different versions of the same resource
+(template, static file, management command, translation), the application
+listed first in :setting:`INSTALLED_APPS` has precedence.
+
 .. setting:: INTERNAL_IPS
 
 INTERNAL_IPS
diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt
index b559445e7c..fced7a7508 100644
--- a/docs/releases/1.7.txt
+++ b/docs/releases/1.7.txt
@@ -697,6 +697,18 @@ following changes that take effect immediately:
 * The ``only_installed`` argument of ``get_model`` and ``get_models`` no
   longer exists, nor does the ``seed_cache`` argument of ``get_model``.
 
+Management commands and order of :setting:`INSTALLED_APPS`
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When several applications provide management commands with the same name,
+Django loads the command from the application that comes first in
+:setting:`INSTALLED_APPS`. Previous versions loaded the command from the
+applicatino that came last.
+
+This brings discovery of management commands in line with other parts of
+Django that rely on the order of :setting:`INSTALLED_APPS`, such as static
+files, templates, and translations.
+
 Behavior of ``LocMemCache`` regarding pickle errors
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~