Re: [Python-Dev] Recent changes to TextIOWrapper and its tests

2013-03-20 Thread Jeff Allen
On 19/03/2013 08:03, Serhiy Storchaka wrote: On 18.03.13 22:26, Jeff Allen wrote: The puzzle is that it requires t.read() to succeed. When I insert a check for bytes type in all the places it seems necessary in my code, I pass the first two conditions, but since t.read() also raises TypeError,

Re: [Python-Dev] Recent changes to TextIOWrapper and its tests

2013-03-19 Thread Serhiy Storchaka
On 18.03.13 22:26, Jeff Allen wrote: The puzzle is that it requires t.read() to succeed. When I insert a check for bytes type in all the places it seems necessary in my code, I pass the first two conditions, but since t.read() also raises TypeError, the overall test fails. Is reading the stream

Re: [Python-Dev] Recent changes to TextIOWrapper and its tests

2013-03-18 Thread Serhiy Storchaka
On 18.03.13 22:26, Jeff Allen wrote: The puzzle is that it requires t.read() to succeed. When I insert a check for bytes type in all the places it seems necessary in my code, I pass the first two conditions, but since t.read() also raises TypeError, the overall test fails. Is reading the stream

[Python-Dev] Recent changes to TextIOWrapper and its tests

2013-03-18 Thread Jeff Allen
I'm pulling recent changes in the io module across to Jython. I am looking for help understanding the changes in http://hg.python.org/cpython/rev/19a33ef3821d That change set is about what should happen if the underlying buffer does not return bytes when read, but instead, for example, unicode