> On 2 nov. 2014, at 00:53, Michael Manfre <[email protected]> wrote: > > Overall the DEP looks really good.
Thanks! > It's currently assumed that BaseEngine.select_template() will scan the list > in order and return the first one it can load, but it might make sense to > explicitly state that in the DEP. I’ve clarified that in the docstring. > To avoid having 3rd party template engines suffering some of the same > disparity that 3rd party database backends faced, what are your thoughts on > having the jinga2 engine maintained outside of core? This would leave only > the string template reference implementation and the DTL in the core. String template don’t have a concept of “loading” a template; they only support “rendering”. I will have to implement a custom loading infrastructure. That doesn’t make it a very good reference implementation. I even considered scraping it for this reason. So I think we need at least another one in core. I was planning to build and maintain a Mako backend externally so as to check how things looks like from the other side of the fence. Hopefully the well-defined a public API will make the lives of maintainers of third-party template engines easier. Also templates are simpler than databases :-) -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/661AA7FE-0BF3-4A28-8B9D-D8FF554F9687%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
