Guido van Rossum added the comment: We seem to have a failure to communicate. I'm sure your example code "works", but you're not showing what's in the data it receives that is important for the app to read (your example just prints it).
And surely your app should be robust even if the connection is closed *without* ever receiving that data (since it may be lost in transit). If you need an application-level error your design should include it in the protocol, not use the connection closing. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30861> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
