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 pitrou
Recipients johansen, laca, pitrou
Date 2008-08-28.16:33:05
SpamBayes Score 1.1439194e-08
Marked as misclassified No
Message-id <1219941196.48b6d34c9c71f@imp.free.fr>
In-reply-to <1219940732.56.0.569136172918.issue3014@psf.upfronthosting.co.za>
Content
Selon johansen <report@bugs.python.org>:
>
> The problem is present in Python 2.4.4, the version that we're using
> here.  I'm not familiar with the versions keyword that's used here, but
> that's the version for which I'm reporting this bug.

The only changes that may be brought now to the 2.4 branch are security fixes
and nothing else. Bug fixes with a slight risk of changing legitimate behaviour
like the present one, on the other hand, will happen either on the 2.6 branch or
on the 2.7 one.

> To be clear, the problem is that when file_dealloc() sees an EOF, it
> assumes that an error has occurred.  It then checks errno.  However,
> it's possible for file_dealloc() to get an EOF under conditions where
> errno hasn't been set.  In that case, it reports an error with a stale
> value of errno.  This is explained in detail in the initial report.

You still haven't explained what the correct behaviour would be, though.
Must it report an error or not? If it must, then how should this specific error
be detected and how should the error message be phrased?

Thanks in advance.
History
Date User Action Args
2008-08-28 16:39:03pitrousetrecipients: + pitrou, johansen, laca
2008-08-28 16:33:06pitroulinkissue3014 messages
2008-08-28 16:33:06pitroucreate