mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-03 02:23:12 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Enforced unicity of app labels.

Browse source 
Fixed #21679.
This commit is contained in:
Aymeric Augustin 2013-12-31 17:25:57 +01:00
parent c40209dcc0
commit 63137a8304
4 changed files with 36 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

23
docs/releases/1.7.txt
View file

@ -655,6 +655,22 @@ script with::
Otherwise, you will hit ``RuntimeError: App registry isn't ready yet.``
App registry consistency
^^^^^^^^^^^^^^^^^^^^^^^^
It is no longer possible to have multiple installed applications with the same
label. In previous versions of Django, this didn't always work correctly, but
didn't crash outright either.
If you have two apps with the same label, you should create an
:class:`~django.apps.AppConfig` for one of them and override its
:class:`~django.apps.AppConfig.label` there. You should then adjust your code
wherever it references this application or its models with the old label.
You should make sure that your project doesn't import models from applications
that aren't in :setting:`INSTALLED_APPS`. Relations involving such models may
not be created properly. Future versions of Django may forbid this entirely.
Subclassing AppCommand
^^^^^^^^^^^^^^^^^^^^^^
@ -663,13 +679,6 @@ Subclasses of :class:`~django.core.management.AppCommand` must now implement a
``handle_app()``. This method receives an :class:`~django.apps.AppConfig`
instance instead of a models module.
App registry consistency
^^^^^^^^^^^^^^^^^^^^^^^^
You should make sure that your project doesn't import models from applications
that aren't in :setting:`INSTALLED_APPS`. Relations involving such models may
not be created properly.
Introspecting applications
^^^^^^^^^^^^^^^^^^^^^^^^^^