id,summary,reporter,owner,description,type,status,priority,milestone,component,resolution,keywords,cc,parents 339,Let jinja throw errors on undefined variables,Elrond,Elrond,"{{{ #!rst (this is to discuss this and then possibly implement it. Implementing is **very** easy). Currently jinja2 replaces ``{{ not_known }}`` by the empty string. The question is, wether it would be better for it to throw an error? Rationale being: Either it's a typo, or it's an error for the variable to be referenced but not being there. Does that make sense? Enabling this: :: mediagoblin/tools/template.py: @@ -43,6 +43,7 @@ def get_jinja_env(template_loader, locale): template_env = jinja2.Environment( loader=template_loader, autoescape=True, + undefined=jinja2.StrictUndefined, extensions=['jinja2.ext.i18n', 'jinja2.ext.autoescape']) }}}",enhancement,closed,trivial,0.2.1,programming,FIXED,,,