This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skorpeo
Recipients docs@python, martin.panter, skorpeo
Date 2019-01-03.22:07:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMXrOMPB7Qvqwuw0F619u+F6+ejh=PnpcShPTFyQFxcThaqgXA@mail.gmail.com>
In-reply-to <1546546901.23.0.686832241357.issue35649@roundup.psfhosted.org>
Content
Ha, ok that would explain it.  Yes, I think it would indeed be helpful to
update the example, but then again I guess leaving it as is may be a good
way to find out if people are reading the docs.

On Thu, Jan 3, 2019 at 10:21 PM Martin Panter <report@bugs.python.org>
wrote:

>
> Martin Panter <vadmium+py@gmail.com> added the comment:
>
> This was changed in Python 3.2+ in Issue 16723. The response object no
> longer sets the “closed” attribute when it runs out of data; it is only set
> when the “close” method is called. Perhaps the example should be amended so
> that it checks if “read” returned an empty string, rather than checking
> “closed”.
>
> Another problem with the example is that printing the chunk as a bytes
> object can trigger BytesWarning. I would add a “repr” call to avoid that.
>
> ----------
> assignee:  -> docs@python
> components: +Documentation
> nosy: +docs@python, martin.panter
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue35649>
> _______________________________________
>
History
Date User Action Args
2019-01-03 22:07:35skorpeosetrecipients: + skorpeo, docs@python, martin.panter
2019-01-03 22:07:33skorpeolinkissue35649 messages
2019-01-03 22:07:33skorpeocreate