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.

Author martin.panter
Recipients martin.panter, pitrou, serhiy.storchaka
Date 2015-02-01.00:57:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1422752245.98.0.86419368712.issue23099@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2015-02-01 00:57:26martin.pantersetrecipients: + martin.panter, pitrou, serhiy.storchaka
2015-02-01 00:57:25martin.pantersetmessageid: <1422752245.98.0.86419368712.issue23099@psf.upfronthosting.co.za>
2015-02-01 00:57:25martin.panterlinkissue23099 messages
2015-02-01 00:57:25martin.pantercreate