Message115217
> 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? |
|
Date |
User |
Action |
Args |
2010-08-30 14:23:21 | pitrou | set | recipients:
+ pitrou, skip.montanaro, benjamin.peterson, docs@python |
2010-08-30 14:23:20 | pitrou | link | issue9715 messages |
2010-08-30 14:23:19 | pitrou | create | |
|