On Mar 24, 4:13 pm, Malcolm Tredinnick <malc...@pointy-stick.com> wrote: > On Tue, 2009-03-24 at 15:27 -0700, Dave Benjamin wrote: > > In any case, sending a TERM signal to the parent process should cause > > the child to die. There is no reasonable justification for the current > > behavior, IMHO. > > There's a lot of justification for the current behaviour: it's a *lot* > simpler than the change you are proposing we make and maintain forever.
Well, it's simple enough for me to hack around it, so I withdraw my proposal. =) > The development server is intended for single user, simple development > stuff. It runs as a foreground process and ^C stops it very nicely. I admit I am a bit of a daemontools addict. I use it even for single user, simple development. The ability to easily start and stop processes, and the built-in, auto-rotating logs that record output even when apps crash hard are totally worth the effort for me. > If you want anything more than that, use a real webserver. It's easy to > set up mod_wsgi so that it reloads (see [1]). Or use --noreload and > restart if/when you make changes to something (if other people are > viewing it at the same time, random restarts aren't generally going to > be a good idea). > > The goal is, intentionally, to keep the development server simple since > there are numerous options for more functional setups when required. I didn't realize that it was possible to do auto-reloading with WSGI. I was under the assumption that the choice was between mod_python, which reloads unpredictably (unless you use the MaxRequestsPerChild trick), and the standalone server, which reloads reliably but sometimes crashes. I really want the best of both worlds: a reliable, auto-reloading, shared development environment. I now understand that there are many more options than those I've considered. Thanks, Dave --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
