Hi, The docs say, a filter shouldn't raise an Exception. But this does not indicate what would happen if a filter does raise one; it merely says you shouldn't do this, so the result is unspecified.
Actually, during development I'm thankful when an exception turns into a traceback, so that I can easily spot the bug. I think this is current behaviour, isn't it? If so, I'm for documenting this explicitly. After development, when settings.DEBUG is false, I'm for the regular treatment of any programming error: Sending a traceback to the admins, and display the standard error page. If a filter should render into an empty string on error, it can always simply catch the exception. Michael --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
