From: homm Date: Thu, 12 Sep 2013 09:13:51 +0000 (+0400) Subject: clearly describe `r.raw` in Body Content Workflow X-Git-Tag: v2.0~10^2~2 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=3440fca2e8ef4ab7d80ee1c0cfd75c92bb3f2b74;p=services%2Fpython-requests.git clearly describe `r.raw` in Body Content Workflow --- diff --git a/docs/api.rst b/docs/api.rst index 12ae8a8..444ce2f 100644 --- a/docs/api.rst +++ b/docs/api.rst @@ -147,7 +147,7 @@ API Changes * The parameter for streaming requests was changed from ``prefetch`` to ``stream`` and the logic was inverted. In addition, ``stream`` is now - required for chunked response reading. + required for raw response reading. :: diff --git a/docs/user/advanced.rst b/docs/user/advanced.rst index 5a8b9b2..5ef0ffd 100644 --- a/docs/user/advanced.rst +++ b/docs/user/advanced.rst @@ -161,7 +161,7 @@ At this point only the response headers have been downloaded and the connection content = r.content ... -You can further control the workflow by use of the :class:`Response.iter_content` and :class:`Response.iter_lines` methods. +You can further control the workflow by use of the :class:`Response.iter_content` and :class:`Response.iter_lines` methods. Also you can read undecoded body from the underlying urllib3 :class:`urllib3.HTTPResponse` at :class:`Response.raw`. Keep-Alive