summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorNick Pope <nick@nickpope.me.uk>2022-10-29 12:34:22 +0100
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2022-10-29 13:35:15 +0200
commitcc5dc19834c286ab342f56ad188ce481c239164c (patch)
treeae5ee7d1012af03b9b39fbb163f5eff2f80b0bc8 /docs
parentddf3ee6f9e6a0b87dd3ce498f53d7c9d7756f486 (diff)
[4.1.x] Removed obsolete doc reference to asyncio.iscoroutinefunction.
Backport of 970f61fefb148284fb2af63b5cc844279254111a from main
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/http/middleware.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/http/middleware.txt b/docs/topics/http/middleware.txt
index 275f739566..29f379889f 100644
--- a/docs/topics/http/middleware.txt
+++ b/docs/topics/http/middleware.txt
@@ -312,7 +312,7 @@ If your middleware has both ``sync_capable = True`` and
``async_capable = True``, then Django will pass it the request without
converting it. In this case, you can work out if your middleware will receive
async requests by checking if the ``get_response`` object you are passed is a
-coroutine function, using :py:func:`asyncio.iscoroutinefunction`.
+coroutine function, using ``asyncio.iscoroutinefunction``.
The ``django.utils.decorators`` module contains
:func:`~django.utils.decorators.sync_only_middleware`,