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:35:54 +0200
commita882fa22ba7dd82826140e8e7d12309a4603cc07 (patch)
tree0b222fb2174da47e39bb7f95383ccf04cd1829c4
parentd3ee881c8ee523c78ddf25d6aa6d190c94bf70d5 (diff)
[4.0.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 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`,