[issue37699] Explicit mention of raised ValueError's after .detach() of underlying IO buffer

Brian Skinn added the comment: Indeed, I hadn't been thinking about the testing/maintenance burden to CPython or other implementations when I made the suggestion. I no longer have a strong opinion about this change, so I am happy to reject/close. -- resolution: -> rejected stage:

[issue37699] Explicit mention of raised ValueError's after .detach() of underlying IO buffer

Irit Katriel added the comment: What is the advantage of making the doc more specific in this manner? If we do change the doc like this, we need to add unit test ensuring that this is the behaviour, and we need are committing cpython (and all other python implementations) to behave like

[issue37699] Explicit mention of raised ValueError's after .detach() of underlying IO buffer

New submission from Brian Skinn : Once the underlying buffer/stream is .detach()ed from an instance of a subclass of TextIOBase or BufferedIOBase, accession of most attributes defined on TextIOBase/BufferedIOBase or the IOBase parent, as well as calling of most methods defined on

[issue37699] Explicit mention of raised ValueError's after .detach() of underlying IO buffer

Change by Brian Skinn : -- type: enhancement -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: