_io.TextIOWrapper._CHUNK_SIZE ignores underlying buffer size, defaults 8192

Bug report

Bug description:

If I try to read a line from a file containing a very long line using open(path, buffering=n).readline(), it reads in chunks of 8192 regardless of the value of n. I would like it to respect n so that I can reduce the number of syscalls.

I can manually work around this by setting the undocumented attribute _CHUNK_SIZE, but I think this should be done automatically. The number 8192 is hard-coded in _io_TextIOWrapper___init___impl; I propose automatically setting it to the buffer size of the underlying _io.BufferedReader / _io.BufferedWriter / _io.BufferedRandom (if the underlying object is one of those).

docker run --rm -it python:3.14.6 bash
apt-get update && apt-get install -y strace
python3 -c 'print("x"*100000)' > f
# f.readline ignores the buffer size
strace -e trace=read python3 -c 'open("f", buffering=100000).readline()' # calls `read(3, ..., 8192)`
# workaround: set f._CHUNK_SIZE
strace -e trace=read python3 -c 'f = open("f", buffering=100000); f._CHUNK_SIZE = 1000000; f.readline()' # calls `read(3, ..., 1000000)`
# aside: f.buffer.readline respects the buffer size
strace -e trace=read python3 -c 'f = open("f", buffering=100000); f.buffer.readline()' # calls `read(3, ..., 100000)`

CPython versions tested on:

3.14

Operating systems tested on:

Linux

Inizia in Modules/_io/textio.c, in _io_TextIOWrapper___init___impl, dove l’issue identifica la dimensione del bloc codificata direttamente nel codice pari a 8192. Riproduci il comportamento con i comandi open(), readline() e strace forniti, quindi segui come viene esposta la dimensione dell’oggetto sottostante con buffer. Il lavoro è completato quando readline() utilizza quella dimensione del buffer per i tipi di oggetti con buffer pertinenti senza richiedere _CHUNK_SIZE.