The docs say:
*"All messages reaching the django catch-all logger when DEBUG <https://docs.djangoproject.com/en/1.6/ref/settings/#std:setting-DEBUG> is True are sent to the console. They are simply discarded (sent to NullHandler) when DEBUG <https://docs.djangoproject.com/en/1.6/ref/settings/#std:setting-DEBUG> is False."* https://docs.djangoproject.com/en/1.6/topics/logging/#django-s-default-logging-configuration >From reading that, I would (naively?) expect to see tracebacks in the terminal I'm running manage.py runserver, if any of my views raise an exception for example. I don't see any, however. Is this because the exception *is* caught, in that it gets intercepted and turned into the nice django debug page? Am i misinterpreting the docs? If so, would it be worth adding a couple of words of clarification in case anyone else might misread it like me? Assuming anyone is that silly? Of course, I would rather prefer it if exception tracebacks *did* go to the console by default, as well as to mail_admins and/or to a nice django debug page... hp PS minimal repro: django-admin.py startproject myproj python manage.py startapp myapp *urls.py:* from django.conf.urls import patterns, include, url urlpatterns = patterns('', # Examples: url(r'^$', 'myapp.views.home', name='home'), ) *myapp/views.py:* def home(request): raise Exception('arg') -- 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 django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. 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/60d3c4c6-22f8-4de6-a376-6230c33ad0a9%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
