[Python-Dev] News from asyncio
gjcarneiro at gmail.com
Mon Jan 27 12:10:20 CET 2014
On 27 January 2014 10:55, Victor Stinner <victor.stinner at gmail.com> wrote:
> 2014-01-27 Antoine Pitrou <solipsis at pitrou.net>:
> > On Mon, 27 Jan 2014 10:45:37 +0100
> > Victor Stinner <victor.stinner at gmail.com> wrote:
> >> - Tulip #111: StreamReader.readexactly() now raises an
> >> IncompleteReadError if the
> >> end of stream is reached before we received enough bytes, instead of
> >> less bytes than requested.
> > Why not simply EOFError?
> IncompleteReadError has two additionnal attributes:
> - partial: "incomplete" received bytes
> - expected: total number of expected bytes (n parameter of readexactly)
> I prefer to use a different exception to ensure that these attributes
> are present. I don't like having to check "hasattr(exc, ...)".
> Before this change, readexactly(n) returned the partial received bytes
> if the end of the stream was reached.
I had the same doubt. Note also that IncompleteReadError is a subclass of
EOFError, so you can catch EOFError if you like.
> Python-Dev mailing list
> Python-Dev at python.org
Gustavo J. A. M. Carneiro
Gambit Research LLC
"The universe is always one step beyond logic." -- Frank Herbert
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev