diff options
| author | Nick Pope <nick@nickpope.me.uk> | 2022-10-29 12:34:22 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-29 13:34:22 +0200 |
| commit | 970f61fefb148284fb2af63b5cc844279254111a (patch) | |
| tree | 175b853c48744b50b76ba3f3395e7ff5dc5a2f22 /docs | |
| parent | 67bc2f1b9917baec0aeb9e2596454d127178eeff (diff) | |
Removed obsolete doc reference to asyncio.iscoroutinefunction.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/http/middleware.txt | 2 |
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`, |
