Antoine Pitrou <[email protected]> added the comment:
> File I/O and memory I/O would have more uniform in their APIs and thus be
> easier to document, describe and use. Currently, one class is used to do
> file I/O.
That's wrong. Various classes are used for file I/O: FileIO,
Buffered{Reader,Writer,Random}, TextIOWrapper.
> If someone wanted to select between file and memory I/O at runtime it
> wouldn't be possible to just swap the class using the current code.
Why would you swap the class since the constructor arguments would be
different anyway?
----------
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue9715>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
