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 pakal
Recipients pakal
Date 2010-02-06.12:27:04
SpamBayes Score 7.4183286e-06
Marked as misclassified No
Message-id <1265459228.25.0.91197617162.issue7865@psf.upfronthosting.co.za>
In-reply-to
Content
The current semantic of io streams is to swallow IOErrors on close(), eg. in _pyio from the trunk, we have each time constructs like:
try:
     self.flush()
except IOError:
     pass  # If flush() fails, just give up

and in C files :
        /* If flush() fails, just give up */
        if (PyErr_ExceptionMatches(PyExc_IOError))
            PyErr_Clear();

I'd rather advocate letting exceptions flow, as users have the right to know if their io operations lost bytes.
Below is a test case for these swallowed exceptions.


PS : issues like http://bugs.python.org/issue7640 are actually much more crucial, so we shall let them higher priority
History
Date User Action Args
2010-02-06 12:27:08pakalsetrecipients: + pakal
2010-02-06 12:27:08pakalsetmessageid: <1265459228.25.0.91197617162.issue7865@psf.upfronthosting.co.za>
2010-02-06 12:27:06pakallinkissue7865 messages
2010-02-06 12:27:05pakalcreate