➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients benjamin.peterson, docs@python, pitrou, skip.montanaro
Date 2010-08-30.14:23:19
SpamBayes Score 1.4642601e-05
Marked as misclassified No
Message-id <1283178197.3248.7.camel@localhost.localdomain>
In-reply-to <19579.48267.999574.22463@montanaro.dyndns.org>
Content 
> 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?
History
Date User Action Args
2010-08-30 14:23:21pitrousetrecipients: + pitrou, skip.montanaro, benjamin.peterson, docs@python
2010-08-30 14:23:20pitroulinkissue9715 messages
2010-08-30 14:23:19pitroucreate