Author sbt
Recipients petri.lehtinen, pitrou, sbt
Date 2011-11-02.22:28:30
SpamBayes Score 4.41582e-09
Marked as misclassified No
Message-id <1320272910.81.0.281974980124.issue13322@psf.upfronthosting.co.za>
In-reply-to
Content
BufferedReader.readinto() should also raise BlockingIOError according to the docs.  Updated unittest checks for that also.

BTW, The documentation for BufferedIOBase.read() says that BlockingIOError should be raised if nothing can be read in non-blocking mode.  BufferedReader inherits from BufferedIOBase and overrides the read() method.  This is the documentation for BufferedReader.read():

    read([n])
        Read and return n bytes, or if n is not given or negative, 
        until EOF or if the read call would block in non-blocking mode.

This sentence is complete gobbledygook, and it makes no mention of what should happen if nothing can be read in non-blocking mode.   So I presume behaviour for BufferedReader.read() should match the documented behaviour for BufferedIOBase.read().
History
Date User Action Args
2011-11-02 22:28:30sbtsetrecipients: + sbt, pitrou, petri.lehtinen
2011-11-02 22:28:30sbtsetmessageid: <1320272910.81.0.281974980124.issue13322@psf.upfronthosting.co.za>
2011-11-02 22:28:30sbtlinkissue13322 messages
2011-11-02 22:28:30sbtcreate