Django

Code

Ticket #826 (closed: wontfix)

Opened 3 years ago

Last modified 2 years ago

Development server kills itself to reload, causing browser GET failures

Reported by: aaronsw Assigned to: adrian
Milestone: Component: django.contrib.admin
Version: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

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.

Attachments

Change History

11/17/05 09:00:33 changed by aaronsw

  • priority changed from normal to high.

This is driving me up the wall.

11/17/05 12:33:06 changed by eugene@lazutkin.com

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.

11/18/05 10:50:44 changed by sune.kirkeby@gmail.com

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.

See http://code.ibofobi.dk/public/file/trunk/ibofobi/src/ibofobi/utils/developer_http.py.

02/28/06 17:13:09 changed by anonymous

  • status changed from new to closed.
  • resolution set to wontfix.

Add/Change #826 (Development server kills itself to reload, causing browser GET failures)




Change Properties
Action