From 2d472ad05c7fb2a5fe405be46af2062cdb5eaeee Mon Sep 17 00:00:00 2001 From: Aaron Chong Date: Wed, 9 Feb 2022 01:25:33 +0800 Subject: Fixed #33495 -- Improved debug logging message about adapting handlers for middlewares. It's the wrapped handler that's adapted to the wrapping middleware. --- docs/topics/async.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/topics/async.txt b/docs/topics/async.txt index 1cc5a7c15c..90a31b994b 100644 --- a/docs/topics/async.txt +++ b/docs/topics/async.txt @@ -52,9 +52,9 @@ If you want to use these, you will need to deploy Django using Middleware can be built to support :ref:`both sync and async ` contexts. Some of Django's middleware is built like - this, but not all. To see what middleware Django has to adapt, you can turn - on debug logging for the ``django.request`` logger and look for log - messages about *"Synchronous middleware ... adapted"*. + this, but not all. To see what middleware Django has to adapt for, you can + turn on debug logging for the ``django.request`` logger and look for log + messages about *"Asynchronous handler adapted for middleware ..."*. In both ASGI and WSGI mode, you can still safely use asynchronous support to run code concurrently rather than serially. This is especially handy when -- cgit v1.3