The behavior of runserver hanging on a check error seems fine to me. That gives you an opportunity to fix the error without having to manually restart the server afterward -- just the same as if you had a SyntaxError. Am I missing the reason why the behavior is problematic?
On Tuesday, March 7, 2017 at 6:32:45 AM UTC-5, James Pic wrote: > > Thanks for sharing some of your insight Aymeric, if I'm not mistaken then > the auto-reload feature/case invalidates Shai's suggestion: would you > recommend that the runserver process exits with non-zero when a check fails > rather than being stuck waiting for another code change to trigger a > reload, so that we could wrap it in an until loop in bash ? > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/52269166-9d24-478a-95d2-f820786aabbe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
