Opened 14 years ago

Closed 13 years ago

Last modified 13 years ago

#826 closed defect (wontfix)

Development server kills itself to reload, causing browser GET failures

Reported by: aaronsw Owned by: Adrian Holovaty
Component: contrib.admin Version:
Severity: normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


The current development server seems to use a threaded model that kills and restarts the server thread everytime the code changes. Since it takes some time to startup again, this leaves some downtime between when you hit save and when you can view the page. While such a delay is unavoidable, with this model it manifests itself as an inaccessible page as opposed to (if, e.g. CGI was used) simply a delay. This kind of annoyance is simply deadly for development, since it discourages making small changes.

Change History (4)

comment:1 Changed 14 years ago by aaronsw

priority: normalhigh

This is driving me up the wall.

comment:2 Changed 14 years ago by eugene@…

It works for me. Reload time is instanteneous. I never had problem with GET failures. Probably you have some CPU-intensive code running during reloading.

comment:3 Changed 14 years ago by sune.kirkeby@…

If you are on a UNIX-like platform you can try ibofobi.utils.developer_http,
it never closes the socket when reexec'ing, so it should never miss a connection.
You can use that, until Djangos developer HTTP is fixed.


comment:4 Changed 13 years ago by anonymous

Resolution: wontfix
Status: newclosed
Note: See TracTickets for help on using tickets.
Back to Top