[issue23099] BytesIO and StringIO values unavailable when closed

[Martin Panter]

Martin Panter added the comment:

I can live with the wording of StringIO, but personally prefer my v2 patch. I now understand that calling close() for Bytes and StringIO objects is intended to immediately free the memory buffer holding the file data (like deleting a file in Windows). So I think it would be better to document this as a property of the whole object, rather than a special exception for each of the getbuffer(), getvalue() non-file-API methods.

I’m happy to propose a similar wording for the StringIO class if you want to make them consistent.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23099>
_______________________________________