RetroSearch Browse

Thu Nov 13 09:05:32 CET 2014 · https://mail.python.org/pipermail/python-dev/2014-November/136932.html

On Thu, Nov 13, 2014 at 6:34 PM, Charles-François Natali
<cf.natali at gmail.com> wrote:
> 2014-11-12 22:16 GMT+00:00 Buck Golemon <buck.2019 at gmail.com>:
>> This is due to the fix for issue21090, which aimed to un-silence errors
>> which previously went unheard. The fix is for me, as a user, to write a loop
>> that uses os.read and interpretes EIO as EOF. This is what I had hoped
>> file.read() would do for me, however, and what it used to do in previous
>> pythons.
>
>
> There's no reason for read() to interpret EIO as EOF in the general
> case: it was masked in previous versions because of a mere bug. The
> behavior is now correct, although being able to retrieve the data read
> so far in case of a buffered read could be useful.

Every change breaks someone's workflow. http://xkcd.com/1172/

ChrisA

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-November/136932.html below:

[Python-Dev] py34 makes it harder to read all of a pty