Hi, Yes, this happens to me frequently. It happens when editing models.py or something imported by a models.py. It's on my mental dream list of things to fix, but feel free to open a ticket about it if there's not one open already.
Collin On Friday, December 5, 2014 2:00:01 AM UTC-5, Mario De Frutos Dieguez wrote: > > If i understand you correctly, when an error occur the server should not > stop, instead of that it will print the error trace to let you correct the > problem but in my case when an error occur the server show the trace and > stop working or at least it returns to the shell. :S > > What i understand reading the official docuementation is that the expected > behavior is not to exit instead of that the server should show the error > trace to let you fix it > > Am i right? > -- You received this message because you are subscribed to the Google Groups "Django users" 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-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/d1c07e3b-f84e-497d-86ba-919dadeb9052%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
