From ddccecee91601ce790c82b0aa03b2fa751580361 Mon Sep 17 00:00:00 2001 From: Alexerson Date: Fri, 12 May 2023 06:34:47 -0700 Subject: [PATCH] [4.2.x] Fixed #34556 -- Doc'd that StreamingHttpResponse accepts memoryviews and strings iterators. Backport of 599f3e2cda50ab084915ffd08edb5ad6cad61415 from main --- docs/ref/request-response.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/ref/request-response.txt b/docs/ref/request-response.txt index 2c195b6f90..c8e55ea370 100644 --- a/docs/ref/request-response.txt +++ b/docs/ref/request-response.txt @@ -1204,9 +1204,9 @@ The :class:`StreamingHttpResponse` is not a subclass of :class:`HttpResponse`, because it features a slightly different API. However, it is almost identical, with the following notable differences: -* It should be given an iterator that yields bytestrings as content. When - serving under WSGI, this should be a sync iterator. When serving under ASGI, - this is should an async iterator. +* It should be given an iterator that yields bytestrings, :class:`memoryview`, + or strings as content. When serving under WSGI, this should be a sync + iterator. When serving under ASGI, then it should be an async iterator. * You cannot access its content, except by iterating the response object itself. This should only occur when the response is returned to the client: