diff --git a/falcon/asgi/multipart.py b/falcon/asgi/multipart.py index 986230793..e4b3fdce4 100644 --- a/falcon/asgi/multipart.py +++ b/falcon/asgi/multipart.py @@ -222,14 +222,14 @@ async def _iterate_parts(self) -> AsyncIterator[BodyPart]: # NOTE(vytas): Interpretations of RFC 2046, Appendix A, vary # as to whether the closing `--` must be followed by CRLF. - # While, the absolute majority of HTTP clients and browsers + # While the absolute majority of HTTP clients and browsers # do append it as a common convention, it seems that this is # not mandated by the RFC, so we do not require it either. # NOTE(vytas): Certain versions of the Undici client # (Node's fetch implementation) do not follow the convention. if await stream.peek(2) == b'--': - # NOTE(vytas): boundary delimiter + '--' signals the - # end of a multipart form. + # NOTE(vytas): boundary delimiter + '--' signals the end of + # a multipart form. await stream.read(2) break diff --git a/falcon/media/multipart.py b/falcon/media/multipart.py index 3270d5629..99cd8785e 100644 --- a/falcon/media/multipart.py +++ b/falcon/media/multipart.py @@ -385,14 +385,14 @@ def __iter__(self) -> Iterator[BodyPart]: # NOTE(vytas): Interpretations of RFC 2046, Appendix A, vary # as to whether the closing `--` must be followed by CRLF. - # While, the absolute majority of HTTP clients and browsers + # While the absolute majority of HTTP clients and browsers # do append it as a common convention, it seems that this is # not mandated by the RFC, so we do not require it either. # NOTE(vytas): Certain versions of the Undici client # (Node's fetch implementation) do not follow the convention. if stream.peek(2) == b'--': - # NOTE(vytas): boundary delimiter + '--' signals the - # end of a multipart form. + # NOTE(vytas): boundary delimiter + '--' signals the end of + # a multipart form. stream.read(2) break