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 asvetlov, kristjan.jonsson, pje, r.david.murray, steve.dower, tim.golden
Date 2016-08-04.13:18:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1470316733.07.0.509871391395.issue27682@psf.upfronthosting.co.za>
In-reply-to
Content
The traceback looks like wsgiref.close() was called before handle_error() was called (perhaps for a second time?)

We'll probably need a reproducer (as simple as possible please) to debug this further, which might be difficult since it may be tricky to simulate the windows error.  But you might also want to, say, post to python-list and see if anyone can spot a problem with your code.  Could it be that it is calling wsgiref.close at the wrong time?
History
Date User Action Args
2016-08-04 13:18:53r.david.murraysetrecipients: + r.david.murray, pje, kristjan.jonsson, tim.golden, asvetlov, steve.dower
2016-08-04 13:18:53r.david.murraysetmessageid: <1470316733.07.0.509871391395.issue27682@psf.upfronthosting.co.za>
2016-08-04 13:18:53r.david.murraylinkissue27682 messages
2016-08-04 13:18:52r.david.murraycreate