On 5/11/07, Bram - Smartelectronix <[EMAIL PROTECTED]> wrote: > there should be a clear way to trigger exceptions when non-existing > variables are added to the templates.
Again, the reasoning is that it's better to have an empty string (or TEMPLATE_STRING_IF_INVALID, if set) come back than to throw exceptions in this situation; if you mistype a variable name in a base template, do you really want every page of your site throwing "Internal Server Error" pages until you track it down? This is why the TEMPLATE_STRING_IF_INVALID setting exists (and why its use is recommended only for debugging purposes) -- it's a compromise between "completely silent failure" and "a typo in a template brings your site down". -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
