Bill Janssen <bill.jans...@gmail.com> added the comment: > AFAICT, his proposed "quick fix" snippet should be good enough for us.
Depends on what we want. It just suppresses information that's now available. What we'd really like is for the caller to recognize that close() can fail, and should be re-tried if it does. That requires that we signal the error back up and out of the ssl module. It seems to me that any non-blocking code should recognize this and respect it. Again, why does this failure only show up in the FTP test? Why aren't we seeing it elsewhere? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8108> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
