On Mon, Jan 17, 2011 at 10:16 PM, Daniel Moisset <dmois...@machinalis.com> wrote: > On Sat, Jan 15, 2011 at 9:23 PM, Marc Garcia <garcia.m...@gmail.com> wrote: >> Well, I still see that policy a way of hiding symptoms, more than an >> advantage for users, but thank you so much for the explanations >> Russell. >> > > I've also felt the same always... I understand and agree with the > philosophy of "always render parseable templates", and also with not > displaying this issues to the *end user* of the site. But I think a > lot of time could be saved if the exceptions which are (correctly) > masked from the end user should be reported somehow to the site > administrator/developer anyway so he can do something about those.... > And nwo that django has a logging mechanism perhaps inetgration with > that should go very well... > > Is there any interest from the core devs in something like this (a > system to log template rendering exceptions, even when they're masked > from the user)?
I thought I just gave support for exactly that idea... quoting: """Now that we have a logging framework baked into Django, there is an argument to be made that template errors that are silently ignored should, in fact, be logged so that developers can do a post-mortem and identify problems.""" Yours, Russ Magee %-) -- 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.
