From a00efa30d6e5ca220b914415904fff5fa0a6f2c5 Mon Sep 17 00:00:00 2001
From: Tim Graham <timograham@gmail.com>
Date: Mon, 2 Jun 2014 11:35:20 -0400
Subject: [PATCH] Fixed #22748 -- Corrected post_migrate usage example.

Thanks Rudolph for the report.
---
 docs/ref/signals.txt | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/docs/ref/signals.txt b/docs/ref/signals.txt
index ac72147631..29ba74d506 100644
--- a/docs/ref/signals.txt
+++ b/docs/ref/signals.txt
@@ -491,16 +491,21 @@ Arguments sent with this signal:
     The database alias used for synchronization. Defaults to the ``default``
     database.
 
-For example, ``yourapp/management/__init__.py`` could be written like::
+For example, you could register a callback in an
+:class:`~django.apps.AppConfig` like this::
 
+    from django.apps import AppConfig
     from django.db.models.signals import post_migrate
-    import yourapp.models
 
     def my_callback(sender, **kwargs):
         # Your specific logic here
         pass
 
-    post_migrate.connect(my_callback, sender=yourapp.models)
+    class MyAppConfig(AppConfig):
+        ...
+
+        def ready(self):
+            post_migrate.connect(my_callback, sender=self)
 
 post_syncdb
 -----------