From 170255caf43f2d0ae072f0b7a22da90f50bd95b0 Mon Sep 17 00:00:00 2001
From: Tim Graham <timograham@gmail.com>
Date: Mon, 2 Jun 2014 11:35:20 -0400
Subject: [PATCH] [1.7.x] Fixed #22748 -- Corrected post_migrate usage example.
Thanks Rudolph for the report.
Backport of a00efa30d6 from master
---
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 f6a227532c..30a9e9bcdf 100644
--- a/docs/ref/signals.txt
+++ b/docs/ref/signals.txt
@@ -494,16 +494,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
-----------