Sure, and it will do it. And you can even get yourself into a circular import situation and cause it to crash from max-recursion-depth exception.
-- Thadeus On Thu, May 6, 2010 at 1:56 PM, Yarko Tymciurak <[email protected]> wrote: > On May 6, 1:47 pm, Thadeus Burgess <[email protected]> wrote: >> Extend will effectively make the template its parent in the tree. >> >> Include will parse the template, and take its response and stick it in >> the tree at that point. >> >> An included file does not have access to its parents blocks, because >> it is effectively become part of the original template. So an include >> file cannot override any blocks. > > Ok, I see. > > Would it be an error (then) to include a file which contains an > {{extend}}? Does that make sense? > > ... lots to think about.... I do not think we want to get into > namespaces for templates (at least not implicitly). > > ... have to think more; keep raising these points (I have to get on > to other things for today, but will look back here later). > > - Yarko > >> >> -- >> Thadeus >> >> On Thu, May 6, 2010 at 1:42 PM, Yarko Tymciurak >> >> <[email protected]> wrote: >> > s for the old reverse-include, i.e. unnamed: {{include}} --- I >> > have squarely aimed at killing that beast, making it go away, so yes - >> > my entire point is to elimin >
