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 jhylton
Recipients
Date 2003-10-06.03:48:36
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=31392

Patch 595601 is an attempt to address this problem, but it's
incomplete.  The file object API allows an extension to
extract to FILE * and squirrel it away.  That's clearly
unsafe, because it can't participate in a locking scheme
without re-writing extensions.

Shane Hathaway proposed another solution here:
http://mail.python.org/pipermail/python-dev/2003-June/036543.html

The problem in this case is that we cause the call to
close() to raise an exception.  I'd prefer to see the
exception raised elsewhere, because close() seldom fails and
is often closed from routines that are cleaning up at the
end.  On the other hand, this solution would be easier to
implementation, so I'm at least +0 on it.

Let's do one or the other.
History
Date User Action Args
2007-08-23 14:17:21adminlinkissue815646 messages
2007-08-23 14:17:21admincreate