Message 115213 - Python tracker

➜

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	benjamin.peterson
Recipients	benjamin.peterson, docs@python, pitrou, skip.montanaro
Date	2010-08-30.13:32:33
SpamBayes Score	9.838889e-10
Marked as misclassified	No
Message-id	<AANLkTimGdHnz85q4HT2oE+Ri7GqaTcJMU33RujLqod7y@mail.gmail.com>
In-reply-to	<1283174858.84.0.744522501572.issue9715@psf.upfronthosting.co.za>

Content
2010/8/30 Skip Montanaro <report@bugs.python.org>: > > Skip Montanaro <skip@pobox.com> added the comment: > > A couple wording comments: > > "All streams are careful about the type of data you give to them" > would read better as "All streams accept specific types of data". > > "The default mode is ``'r'`` (open for reading text, synonym of > ``'rt'``)". I liked the original wording better. Feel free to change it; it's been committed. > > Finally, not specific to this change, but I wonder if rather than > having distinct io.StringIO and io.BytesIO classes it would be better > to have a single io.MemoryIO class which takes mode arguments just > like io.FileIO? The correspondence between file-based and memory- > based i/o would be more one-to-one. Such a class could be added > without breaking existing code by using the StringIO and BytesIO > classes as the back-end for a MemoryIO class. What advantage would that have?

2010/8/30 Skip Montanaro <report@bugs.python.org>:
>
> Skip Montanaro <skip@pobox.com> added the comment:
>
> A couple wording comments:
>
> "All streams are careful about the type of data you give to them"
> would read better as "All streams accept specific types of data".
>
> "The default mode is ``'r'`` (open for reading text, synonym of
> ``'rt'``)".  I liked the original wording better.

Feel free to change it; it's been committed.

>
> Finally, not specific to this change, but I wonder if rather than
> having distinct io.StringIO and io.BytesIO classes it would be better
> to have a single io.MemoryIO class which takes mode arguments just
> like io.FileIO?  The correspondence between file-based and memory-
> based i/o would be more one-to-one.  Such a class could be added
> without breaking existing code by using the StringIO and BytesIO
> classes as the back-end for a MemoryIO class.

What advantage would that have?

History
Date	User	Action	Args
2010-08-30 13:32:34	benjamin.peterson	set	recipients: + benjamin.peterson, skip.montanaro, pitrou, docs@python
2010-08-30 13:32:33	benjamin.peterson	link	issue9715 messages
2010-08-30 13:32:33	benjamin.peterson	create