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 giampaolo.rodola
Recipients Sam Adams, SilentGhost, giampaolo.rodola, r.david.murray
Date 2016-03-08.19:59:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1457467177.94.0.445689836317.issue25933@psf.upfronthosting.co.za>
In-reply-to
Content
It looks to me that forcing self.voidresp() in case the callback raises an exception is a bad idea: it may easily end up hanging if the server is not supposed to send a response at that point (see: the transfer is not finished).

As for the issue per se: I think there's nothing wrong with the current behavior except perhaps we could provide a better error message. But in order to do that we should check file mode before hand and relying on the file mode is also not a good idea IMO because the file object can be anything.
History
Date User Action Args
2016-03-08 19:59:38giampaolo.rodolasetrecipients: + giampaolo.rodola, r.david.murray, SilentGhost, Sam Adams
2016-03-08 19:59:37giampaolo.rodolasetmessageid: <1457467177.94.0.445689836317.issue25933@psf.upfronthosting.co.za>
2016-03-08 19:59:37giampaolo.rodolalinkissue25933 messages
2016-03-08 19:59:37giampaolo.rodolacreate