summaryrefslogtreecommitdiff
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:36:23 +0200
commitf6f0699d01f5840437bfd236c76c797943ef8edc (patch)
treeae08ed6d9dae005adf057b568c0b8fe08a3e5ddb
parentaccdd0576d50b4696378ed1ab651c20affcae08b (diff)
[3.2.x] Removed obsolete doc reference to asyncio.iscoroutinefunction.
Backport of 970f61fefb148284fb2af63b5cc844279254111a from main
-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 aa89f79e0c..d82a3f6ae8 100644
--- a/docs/topics/http/middleware.txt
+++ b/docs/topics/http/middleware.txt
@@ -314,7 +314,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`,