id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
21018	Make the implications of order in INSTALLED_APPS more consistent	Kevin Christopher Henry	nobody	"There are several subsystems that are affected by the order of the apps in `INSTALLED_APPS`. These include (at least): templates, static files, translations, and management commands. For the first three, the rule is that the first listed app has precedence: it will be used in preference to any app listed later that uses the same name for something (e.g. a template, file, or translation).

In the case of management commands, however, the semantics are just the opposite: precedence is given to apps that are listed later.

The proposal is to fix this so that management commands follow the same ordering rules as the other subsystems. This is an easy fix, but it has implications for backwards compatibility: specifically, for any project that currently has two apps in `INSTALLED_APPS` that define the same command, the one that is actually used will change. (Note that this does not apply to the case of apps overriding core management commands; they will continue to do so.)

See [https://groups.google.com/forum/#!topic/django-developers/r37clRaXgf4 here] for a discussion of the issue.

See #20914 for a proposal to document more thoroughly the issue of order in `INSTALLED_APPS`.
 "	Cleanup/optimization	closed	Core (Management commands)	dev	Normal	fixed	app-loading	k@… Kevin Christopher Henry mmitar@… esauro django@…	Accepted	0	0	0	0	0	0