Antoine Pitrou <pit...@free.fr> added the comment: It is not strictly speaking "an error" which is causing the double close... It's the deliberate behaviour of a test I have added to check that errno is correctly set on the raised IOError when calling close() on a FileIO object whose handle has already been closed manually (with os.close()).
In other words, since it is possible to retrieve the file descriptor of an IO object using the fileno() method (and, moreover, it is possible to give an existing file descriptor to the open() function so as to wrap it inside an IO object), access to a closed file is always possible and should be protected against (that is, it raises an IOError with the errno attribute equal to EBADF). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5544> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
