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 johansen
Recipients johansen, laca, pitrou
Date 2008-08-28.16:24:31
SpamBayes Score 1.1756091e-08
Marked as misclassified No
Message-id <1219940732.56.0.569136172918.issue3014@psf.upfronthosting.co.za>
In-reply-to
Content
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.

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.  I
don't think the title is misleading; it's incorrect for file_dealloc()
to assume that errno is set every time it gets an EOF.
History
Date User Action Args
2008-08-28 16:25:32johansensetrecipients: + johansen, pitrou, laca
2008-08-28 16:25:32johansensetmessageid: <1219940732.56.0.569136172918.issue3014@psf.upfronthosting.co.za>
2008-08-28 16:24:32johansenlinkissue3014 messages
2008-08-28 16:24:31johansencreate