[issue37846] declare that Text I/O use buffer inside

Inada Naoki added the comment: I still think it's too detailed. Reading C and Python code is much better way to understand such implementation detail. -- resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker

[issue37846] declare that Text I/O use buffer inside

Windson Yang added the comment: I found the document is not that clear when I try to understand what happens when Python read/write a file. I'm not sure who also needs this information. As you said, It wouldn't help the user program in Python. However, make it more clear maybe help users

[issue37846] declare that Text I/O use buffer inside

Inada Naoki added the comment: It's just an implementation detail. Python implementation and C implementation behave slightly different. But user program shouldn't rely on the detail. Why do you think implementation details should be declared? Who needs the information? -- nosy:

[issue37846] declare that Text I/O use buffer inside

New submission from Windson Yang : At the beginning of https://docs.python.org/3.7/library/io.html#io.RawIOBase, we declared that > Binary I/O (also called buffered I/O) and > 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.