summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAdam Johnson <me@adamj.eu>2019-10-28 12:31:23 +0000
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2019-10-28 13:32:09 +0100
commit4c0979bba4f5ec31f5b5c523c26ae53b38b212f9 (patch)
tree40a32d3c085e15154d0c00f0293f99125ca7db30
parent48df40262bb13ff923dcbafc2bc70af12fe9db47 (diff)
downloaddjango-4c0979bba4f5ec31f5b5c523c26ae53b38b212f9.tar.gz
[2.2.x] Documented the order in which signal receivers are called.
Backport of ab0fd3f58f751859cc7c5260decf0acca26513bf from master
-rw-r--r--docs/topics/signals.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/topics/signals.txt b/docs/topics/signals.txt
index fc7c641af1..df23875d3f 100644
--- a/docs/topics/signals.txt
+++ b/docs/topics/signals.txt
@@ -49,7 +49,8 @@ Listening to signals
To receive a signal, register a *receiver* function using the
:meth:`Signal.connect` method. The receiver function is called when the signal
-is sent.
+is sent. All of the signal's receiver functions are called one at a time, in
+the order they were registered.
.. method:: Signal.connect(receiver, sender=None, weak=True, dispatch_uid=None)