#9582: Unhandled exception in runserver (when losing network file?)
------------------------------------+---------------------------------------
Reporter: MattLabbe | Owner: nobody
Status: closed | Milestone:
Component: Uncategorized | Version: 1.0
Resolution: invalid | Keywords: exception runserver
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by kmtracey):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
I think you'd need to do more than lose network connectivity to cause
this. The code from !SocketServer.py that is running into trouble is:
{{{
#!python
def handle_request(self):
"""Handle one request, possibly blocking."""
try:
request, client_address = self.get_request()
except socket.error:
return
}}}
It's the `except socket.error` that has raised the !AttributeError, but
socket was imported earlier via `import socket` so it's a bit odd for it
to now be None. In fact it looks likes this Python issue:
http://bugs.python.org/issue1731 A fix for that has been put into Python
2.5, from the timing it looks like you need 2.5.2 to have it so I suspect
you are running 2.5.1?
I don't know that there's much useful we could do to 'fix' this in the dev
server. Apparently the world is coming to an end and things are not
necessarily being cleaned up in the right order, resulting in a spurious
traceback. Even if we tried to do something (what?) it isn't clear any of
our code would behave any better than the !SocketServer code given the
state things have gotten into.
Reopen if you've got a recreatable scenario where this happens, and some
evidence that it's not in fact due to that Python issue...and indicate
what you think would be better to do that what currently happens?
--
Ticket URL: <http://code.djangoproject.com/ticket/9582#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
