Note that this is a fully unbuffered read.
On Wed, Nov 12, 2014 at 11:34 PM, Charles-François Natali <
cf.nat...@gmail.com> wrote:
> 2014-11-12 22:16 GMT+00:00 Buck Golemon :
> > This is due to the fix for issue21090, which aimed to un-silence errors
> > which previously went unheard. The fix is
On Thu, Nov 13, 2014 at 6:34 PM, Charles-François Natali
wrote:
> 2014-11-12 22:16 GMT+00:00 Buck Golemon :
>> 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 interprete
2014-11-12 22:16 GMT+00:00 Buck Golemon :
> 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,
This code works as expected in python <3.4 (printing 'ok' then an error),
but only gives an error in python3.4.
```
import os
read_fd, write_fd = os.openpty()
os.write(write_fd, b'ok\n')
os.close(write_fd)
read_file = os.fdopen(read_fd, 'rb', 0)
print("read: %r" % read_file.read())
print("read: %
