Message172945
You guessed it Graham! Bob Brewer pointed me to your post while I was fighting with this, which led me to testing the behavior under various servers and finding the wsgiref issue.
Current Django trunk doesn't have its own finish_response anymore for the dev server; it's using the one on wsgiref's BaseHandler. So Django's problem should get fixed when wsgiref's does.
I'm working on a test of the simpler case of ensuring that close() is called when any old exception is raised during the response. A test that actually sets up a socket and tests the client disconnecting would be a lot more complicated and a bit out of step with the current wsgi tests that all seem to use a socket-less mock. |
|
Date |
User |
Action |
Args |
2012-10-15 05:19:58 | btubbs | set | recipients:
+ btubbs, jcea, pje, pitrou, grahamd |
2012-10-15 05:19:58 | btubbs | set | messageid: <1350278398.38.0.616265483664.issue16220@psf.upfronthosting.co.za> |
2012-10-15 05:19:58 | btubbs | link | issue16220 messages |
2012-10-15 05:19:57 | btubbs | create | |
|