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 r.david.murray
Recipients SG, asvetlov, berker.peksag, iMath, kristjan.jonsson, pje, r.david.murray, steve.dower, tim.golden
Date 2016-08-09.14:17:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1470752269.99.0.213636097074.issue27682@psf.upfronthosting.co.za>
In-reply-to
Content
Kristján: right, what I'm saying about the possible bug is the final part of the traceback resulting from (apparently) wsgiref being closed and a new operation being attempted.  *Probably* that is a django bug in handling a network error, but maybe it is a wsgiref bug in handling the network error.  (I'm assuming here that the Windows error is triggered by the retry, but I could of course be completely wrong about that.)
History
Date User Action Args
2016-08-09 14:17:50r.david.murraysetrecipients: + r.david.murray, pje, kristjan.jonsson, tim.golden, asvetlov, berker.peksag, steve.dower, iMath, SG
2016-08-09 14:17:49r.david.murraysetmessageid: <1470752269.99.0.213636097074.issue27682@psf.upfronthosting.co.za>
2016-08-09 14:17:49r.david.murraylinkissue27682 messages
2016-08-09 14:17:49r.david.murraycreate