From e50e0ee27bf16090fe36a87cf91fe2baa27b70f1 Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Sat, 11 Oct 2014 16:03:35 +0200 Subject: [PATCH] Fixed #23618 -- Allowed apps with no models to still have migrations Basically a4737bf6ae reapplied. --- django/db/migrations/loader.py | 2 -- docs/releases/1.8.txt | 3 +++ 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/django/db/migrations/loader.py b/django/db/migrations/loader.py index 9a3dd80d47..64d24adef8 100644 --- a/django/db/migrations/loader.py +++ b/django/db/migrations/loader.py @@ -63,8 +63,6 @@ class MigrationLoader(object): self.unmigrated_apps = set() self.migrated_apps = set() for app_config in apps.get_app_configs(): - if app_config.models_module is None: - continue # Get the migrations module directory module_name = self.migrations_module(app_config.label) was_loaded = module_name in sys.modules diff --git a/docs/releases/1.8.txt b/docs/releases/1.8.txt index 6fa91e5ab3..6b08e2b5a1 100644 --- a/docs/releases/1.8.txt +++ b/docs/releases/1.8.txt @@ -276,6 +276,9 @@ Migrations * The :class:`~django.db.migrations.operations.RunSQL` operation can now handle parameters passed to the SQL statements. +* It is now possible to have migrations (most probably :ref:`data migrations + `) for applications without models. + Models ^^^^^^