This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients Dima.Tisnek, gvanrossum, pfreixes, yselivanov
Date 2017-07-06.21:52:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1499377979.82.0.105084839661.issue30861@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2017-07-06 21:52:59gvanrossumsetrecipients: + gvanrossum, Dima.Tisnek, yselivanov, pfreixes
2017-07-06 21:52:59gvanrossumsetmessageid: <1499377979.82.0.105084839661.issue30861@psf.upfronthosting.co.za>
2017-07-06 21:52:59gvanrossumlinkissue30861 messages
2017-07-06 21:52:59gvanrossumcreate