"Guido van Rossum" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
| Changing the mode between text and binary is not feasible (since it
| would have to change the class). But it is perfectly acceptable to use
| sys.std{in,out}.buffer if you need to write a binary transparent
| filter.
In PEP 3116, the Buffered I/O section has
Additionally, the abstract base class provides one member variable:
.raw
A reference to the underlying RawIOBase object.
The Text I/O section does *not* have, but I presume should, similar lines
about member variable .buffer.
Perhaps a note could be added that stdin/out will be Text I/O and that the
bytes buffer is easily unwrapped via .buffer (and even via .raw).
While I sympathize with the initial surprise, I am willing to type .buffer
should I need to. The real problem is that 2to3.py cannot do so
automatically (and be always. and probably not even usually, correct).
tjr
_______________________________________________
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
