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 pfreixes
Recipients gvanrossum, pfreixes, yselivanov
Date 2017-07-05.22:00:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
One of the disadvantages with the Exception is that you are relying on
how the events are being succeeded, and this is something that you
can't predict. With just a different delay between the data and the
RST packet and you might get the data in two different ways, either
via a regular read or via one adhoc Exception.

This might be confusing for the developer and will end up with the
second thing that IMHO is also important, the code that has to be
produced by the developer gets complicated.

On Wed, Jul 5, 2017 at 11:29 PM, Yury Selivanov <> wrote:
> Yury Selivanov added the comment:
>> But IMHO the example it's just that an example, if the connection at
> some point was not broken/closed/... and some data came into the
> buffer, this data should be put available for the user.
> In my experience, you never want to recover any data from broken connections.  In cases where it's safe, StreamReader attaches the buffered data to the exception (see IncompleteReadError).
> ----------
> _______________________________________
> Python tracker <>
> <>
> _______________________________________
Date User Action Args
2017-07-05 22:00:47pfreixessetrecipients: + pfreixes, gvanrossum, yselivanov
2017-07-05 22:00:47pfreixeslinkissue30861 messages
2017-07-05 22:00:47pfreixescreate