mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-07-06 18:59:13 +00:00
Code Issues 32 Releases Wiki Activity

[5.2.x] Fixed typo in docs/topics/signals.txt.

Browse Source 
Backport of e2b9a179133ebca9773c5c259f6a7d27489cf141 from main
This commit is contained in:
mguegnol 2025-03-23 12:02:42 -07:00 committed by Mariusz Felisiak
parent 280523bbd8
commit 45eed2c9dc
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/topics/signals.txt
View File

@ -314,7 +314,7 @@ Whether synchronous or asynchronous, receivers will be correctly adapted to
whether ``send()`` or ``asend()`` is used. Synchronous receivers will be whether ``send()`` or ``asend()`` is used. Synchronous receivers will be
called using :func:`~.sync_to_async` when invoked via ``asend()``. Asynchronous called using :func:`~.sync_to_async` when invoked via ``asend()``. Asynchronous
receivers will be called using :func:`~.async_to_sync` when invoked via receivers will be called using :func:`~.async_to_sync` when invoked via
``sync()``. Similar to the :ref:`case for middleware <async_performance>`, ``send()``. Similar to the :ref:`case for middleware <async_performance>`,
there is a small performance cost to adapting receivers in this way. Note that there is a small performance cost to adapting receivers in this way. Note that
in order to reduce the number of sync/async calling-style switches within a in order to reduce the number of sync/async calling-style switches within a
``send()`` or ``asend()`` call, the receivers are grouped by whether or not ``send()`` or ``asend()`` call, the receivers are grouped by whether or not