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 Windson Yang
Recipients Windson Yang, docs@python
Date 2019-08-14.02:44:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
At the beginning of, we declared that 

> Binary I/O (also called buffered I/O)
> Raw I/O (also called unbuffered I/O)

But we didn't mention if Text I/O use buffer or not which led to confusion. Even though we talked about it later in

> The TextIOBase ABC, another subclass of IOBase, deals with streams whose bytes represent text, and handles encoding and decoding to and from strings. TextIOWrapper, which extends it, is a buffered text interface to a buffered raw stream (BufferedIOBase). Finally, StringIO is an in-memory stream for text.

IMO, it will be better to declare 'Reads and writes are internally buffered in order to speed things up' at the very beginning in 

> Text I/O
> Text I/O expects and produces str objects...

or maybe

> class io.TextIOBase
> Base class for text streams. This class provides a character and line based interface to stream I/O. It inherits IOBase. There is no public constructor.
Date User Action Args
2019-08-14 02:44:09Windson Yangsetrecipients: + Windson Yang, docs@python
2019-08-14 02:44:09Windson Yangsetmessageid: <>
2019-08-14 02:44:09Windson Yanglinkissue37846 messages
2019-08-14 02:44:08Windson Yangcreate