summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAdam Johnson <me@adamj.eu>2019-09-25 10:28:08 +0100
committerAdam Johnson <me@adamj.eu>2019-09-25 10:40:49 +0100
commit80d78fd651b331a4a478c22d8b0f5c0f52120fa5 (patch)
tree6ed48fa04958288a77a9fd720cc24f47b8e8c5bc
parentacc0d99e6c1388199ca2275b179051e5a89cdc25 (diff)
downloaddjango-80d78fd651b331a4a478c22d8b0f5c0f52120fa5.tar.gz
[2.2.x] Documented admonition on when to use custom signals
Thanks Cesar Canassa for the suggestion and Aymeric Augustin for review. Backport of 566fca14b3e1406f918898de5bb2b2382a44edaf from master
-rw-r--r--docs/topics/signals.txt6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/topics/signals.txt b/docs/topics/signals.txt
index 80a92d7a9c..fc7c641af1 100644
--- a/docs/topics/signals.txt
+++ b/docs/topics/signals.txt
@@ -206,6 +206,12 @@ Defining and sending signals
Your applications can take advantage of the signal infrastructure and provide
its own signals.
+.. admonition:: When to use custom signals
+
+ Signals are implicit function calls which make debugging harder. If the
+ sender and receiver of your custom signal are both within your project,
+ you're better off using an explicit function call.
+
Defining signals
----------------