Fixed #22028 -- Documented that database signals aren't emitted for apps that laack a models module.

Thanks un33k for the suggestion and donjpacheco for the draft patch.

2 files changed, 7 insertions, 2 deletions

diff --git a/docs/ref/applications.txt b/docs/ref/applications.txt
index 2a5128ebb8..b31f00337c 100644
--- a/docs/ref/applications.txt
+++ b/docs/ref/applications.txt
@@ -194,6 +194,10 @@ Read-only attributes
     from 'django/contrib/admin/models.pyc'>``.
 
     It may be ``None`` if the application doesn't contain a ``models`` module.
+    Note that the database related signals such as
+    :data:`~django.db.models.signals.pre_migrate` and
+    :data:`~django.db.models.signals.post_migrate`
+    are only emitted for applications that have a ``models`` module.
 
 Methods
 -------
diff --git a/docs/ref/signals.txt b/docs/ref/signals.txt
index 6f1b3029e5..25def4490d 100644
--- a/docs/ref/signals.txt
+++ b/docs/ref/signals.txt
@@ -377,7 +377,7 @@ pre_migrate
    :module:
 
 Sent by the :djadmin:`migrate` command before it starts to install an
-application.
+application. It's not emitted for applications that lack a ``models`` module.
 
 Any handlers that listen to this signal need to be written in a particular
 place: a ``management`` module in one of your :setting:`INSTALLED_APPS`. If
@@ -469,7 +469,8 @@ post_migrate
    :module:
 
 Sent by the :djadmin:`migrate` command after it installs an application, and the
-:djadmin:`flush` command.
+:djadmin:`flush` command. It's not emitted for applications that lack a
+``models`` module.
 
 Any handlers that listen to this signal need to be written in a particular
 place: a ``management`` module in one of your :setting:`INSTALLED_APPS`. If