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 jasujm
Recipients jasujm, neologix, pitrou, serhiy.storchaka
Date 2013-05-15.09:04:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368608698.04.0.886585927492.issue17976@psf.upfronthosting.co.za>
In-reply-to
Content
I tried to reply to the review of my last patch but this tracker software itself crashed. Is there anyone who would be interested in the traceback?

Anyway, I'll reply here.

On 2013/05/15 08:37:29, Charles-François Natali wrote:
> http://bugs.python.org/review/17976/diff/8158/Objects/fileobject.c
> File Objects/fileobject.c (right):
> 
> http://bugs.python.org/review/17976/diff/8158/Objects/fileobject.c#newcode1856
> Objects/fileobject.c:1856: if (n2 != n || errno != 0) {
> Hum, we saw that ferror() could be used to detect the error, so it should be
> used instead.
> 
> Also, there's a problem with this patch: it's checking errno too late: for
> example, it could have been cleared by FILE_END_ALLOW_THREADS or Py_XDECREF in
> the meantime.

Ok. However I must point out that if errno is cleared in the meantime, that also affects PyErr_SetFromErrno. I've submitted another patch where I'm extra careful with errno.
History
Date User Action Args
2013-05-15 09:04:58jasujmsetrecipients: + jasujm, pitrou, neologix, serhiy.storchaka
2013-05-15 09:04:58jasujmsetmessageid: <1368608698.04.0.886585927492.issue17976@psf.upfronthosting.co.za>
2013-05-15 09:04:58jasujmlinkissue17976 messages
2013-05-15 09:04:57jasujmcreate