Hi there! > In fact, it allows arbitrary nesting and combinations. It works by > keeping a list of possible sources for each template and as template > is rendered it removes it from the list, so that next time it is not > loaded anymore.
I'm not entirely convinced about maintaining a dicts of lists in the template context containing the template candidates. I didn't work on this issue lately but I managed to write a little article about it[0], kind of for my own purposes. In there I try to come with a way of knowing what would the next template to be rendered be without storing continuously a list of templates. Of course, the system I'm purposing could be totally wrong and don't have any sense, so let me know what you think about it ;) [0] http://unaizalakain.info/2013/12/19/self-referenced-template-inheritance-with-django/
signature.asc
Description: PGP signature
