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.

classification
Title: Should io.TextIOWrapper raise an error at instantiation if a StringIO is passed as 'buffer'?
Type: behavior Stage:
Components: Library (Lib) Versions: Python 3.9, Python 3.8
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: bskinn
Priority: normal Keywords:

Created on 2019-09-04 16:09 by bskinn, last changed 2022-04-11 14:59 by admin.

Messages (1)
msg351139 - (view) Author: Brian Skinn (bskinn) * Date: 2019-09-04 16:09
If I read the docs correctly, io.TextIOWrapper is meant to provide a str-typed interface to an underlying bytes stream.

If a TextIOWrapper is instantiated with the underlying buffer=io.StringIO(), it breaks:

>>> import io
>>> tw = io.TextIOWrapper(io.StringIO())
>>> tw.write(b'abcd\n')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: write() argument must be str, not bytes
>>> tw.write('abcd\n')
5
>>> tw.read()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: string argument expected, got 'bytes'
>>> tw.read(1)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: underlying read() should have returned a bytes-like object, not 'str'



Would it be better for TextIOWrapper to fail earlier, at instantiation-time, for this kind of (unrecoverably?) broken type mismatch?
History
Date User Action Args
2022-04-11 14:59:19adminsetgithub: 82210
2019-09-04 16:09:55bskinncreate