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 lemburg
Recipients brett.cannon, eric.araujo, lemburg, loewis, meatballhat, pitrou, rhettinger, vstinner
Date 2011-05-23.22:02:04
SpamBayes Score 6.6498e-07
Marked as misclassified No
Message-id <>
In-reply-to <1306185807.3548.0.camel@localhost.localdomain>
Antoine Pitrou wrote:
> Antoine Pitrou <> added the comment:
>> TextIOWrapper() is conceptually something completely different. It's
>> more something like StreamReaderWriter().
> That's a rather strange assertion. Can you expand?
> TextIOWrapper supports read-only, write-only, read-write, unseekable and
> seekable streams.

StreamReader and StreamWriter classes provide the base codec
implementations for stateful interaction with streams. They
define the interface and provide a working implementation for
those codecs that choose not to implement their own variants.

Each codec can, however, implement variants which are optimized
for the specific encoding or intercept certain stream methods
to add functionality or improve the encoding/decoding

Both are essential parts of the codec interface.

TextIOWrapper and StreamReaderWriter are merely wrappers
around streams that make use of the codecs. They don't
provide any codec logic themselves. That's the conceptual
Date User Action Args
2011-05-23 22:02:05lemburgsetrecipients: + lemburg, loewis, brett.cannon, rhettinger, pitrou, vstinner, eric.araujo, meatballhat
2011-05-23 22:02:04lemburglinkissue8796 messages
2011-05-23 22:02:04lemburgcreate