From f44dbf74a4abf9c45d49568c7ca46363ff6e5112 Mon Sep 17 00:00:00 2001 From: Andrew Godwin Date: Fri, 25 Jul 2014 09:09:15 -0700 Subject: Mark initial_data as deprecated separately from syncdb. Refs #23077. --- docs/internals/deprecation.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs/internals') diff --git a/docs/internals/deprecation.txt b/docs/internals/deprecation.txt index cc219343a3..f1cdfdb6be 100644 --- a/docs/internals/deprecation.txt +++ b/docs/internals/deprecation.txt @@ -28,10 +28,6 @@ about each item can often be found in the release notes of two versions prior. * The ``DatabaseCreation`` class on each database backend will be removed, and all table/schema editing will be moved to be via ``SchemaEditor`` instead. -* The legacy method of syncing apps without migrations will be removed, - and migrations will become compulsory for all apps. This includes automatic - loading of fixtures and support for initial SQL data. - * The ability to :func:`~django.core.urlresolvers.reverse` URLs using a dotted Python path will be removed. @@ -68,6 +64,10 @@ details on these changes. * ``allow_syncdb`` on database routers will no longer automatically become ``allow_migrate``. +* The legacy method of syncing apps without migrations will be removed, + and migrations will become compulsory for all apps. This includes automatic + loading of ``initial_data`` fixtures and support for initial SQL data. + * All models will need to be defined inside an installed application or declare an explicit :attr:`~django.db.models.Options.app_label`. Furthermore, it won't be possible to import them before their application -- cgit v1.3