Hi, The development server currently uses "non-daemon threads" for the socketserver, this has many bad side effects, as discussed in ticket #21773 ( https://code.djangoproject.com/ticket/21773 ). The most annoying disadvantages of that are: 1) Longer time to restart, because the sever has to make sure everything is finished before it can auto-reload, I don't think this is a good behavior because since it's a development server, you are always intentionally causing the auto-reload. 2) If something goes wrong, like a bad view, there is no way to quit or restart the server, without manually killing its process from the OS.
I made a patch: https://github.com/django/django/pull/2690 that changes the default threads type of the server to be daemon threads, and introduced a command option "runserver --nodaemon" to use non-daemon threads if the user still prefers that for one reason or another. I'm aware that the core developers are reluctant to merge any big change without a discussion first, so I'm asking about your opinions about that change and the patch. Thanks a lot, Moayad -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/b1bf66a0-d6aa-4168-a566-6d8a099a7096%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
