On Nov 8, 8:12 am, Phlip <phlip2...@gmail.com> wrote: > I just need the usual features - to log the actual error, and stick it > in the programmer's face during a test run. > > But when I Google for this subject, I get ten thousand newbies asking > why they got some other error, and self.handle_uncaught_exception > appears in their stack trace!
If nobody turns up a nice high-level way (besides overriding django.contrib.messages.middleware.MessageMiddleware and sticking the resulting class back into MIDDLEWARE_CLASSES), this settings.py option simply lets the errors fly: DEBUG_PROPAGATE_EXCEPTIONS = True > -- > Phlip > http://bit.ly/ZeekLand -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
