Antoine Pitrou <pit...@free.fr> added the comment: > If everyone agrees on "error: [Errno 0] Error" being a legitimate alias > for a "connection closed event" condition then I'd say the test server > looks good, even if I think that expecting a ssl.SSLError derived > exception would have made more sense, but I understand this is a > OpenSSL inherited behavior.
Well, it's quite an unfortunate error display, so perhaps we could detect it and turn into something more meaningful instead. However, I think it should remain a socket error or an OS error, because it's really the underlying socket which is closed, not the SSL wrapper. > Anyway, I'd like to improve the SSL test server in future as I'm sure > it > hides some other problems but I can do that once pyftpdlib's SSL > server code is more mature and after 2.7 is released. Shouldn't it become part of asyncore at some point? It's both useful (well, for people using asyncore anyway :-)) and non-trivial. ---------- _______________________________________ 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
