Re: intended security model for templates

Personally I feel it's exposing too much implementation to the template authors. Whilst I can understand the appeal of allowing namespacing of template libs, I think exposing full python paths is the wrong approach. Perhaps allowing a "app_label:libname" approach to being more specific? -- Curti

intended security model for templates

I was hoping to get clarification on what security model we intend to support for template authors. In ticket #12772 it's proposed to allow loading template tags using a dotted Python path. This would allow template authors to trigger imports of any