[3.0.x] Documented admonition on when to use custom signals
Thanks Cesar Canassa for the suggestion and Aymeric Augustin for review.
Backport of 566fca14b3
from master
This commit is contained in:
parent
fcaaff9862
commit
f4b7acedbf
|
@ -206,6 +206,12 @@ Defining and sending signals
|
||||||
Your applications can take advantage of the signal infrastructure and provide
|
Your applications can take advantage of the signal infrastructure and provide
|
||||||
its own signals.
|
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
|
Defining signals
|
||||||
----------------
|
----------------
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue