Nidan added the comment: Why should asynchat.handle_read care about closed sockets if asyncore.recv does that already? Currently asynchat.handle_read handles empty strings from asycore.recv gracefully (by doing some unnecessary work aka executing the remainder of the function), it doesn't treat them specially. The only path that might cause asynchat.handle_read to close the socket requires asycore.recv to throw. Introducing None as possible return value from asyncore.recv therefore seems unnecessary to me.
Changed the patch accordingly. ---------- Added file: http://bugs.python.org/file30088/issue16133.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16133> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
