Hi,
On May 24, 10:58 am, Jonathan Slenders <[email protected]> wrote: > I guess this is a flaw in the inheritance algorithm, only the most > outer blocks should be used during the resolving of inheritance. How else would it work? Think of a block like a function plus the execution of that function. By placing a new block within a block you want that behavior and if you override a block and in that another block that already existed both Jinja2 and Django will have to also immediately call it. There is only one rule: if you don't like that, make the block toplevel. The only alternative sane semantic would be raising a runtime error, but I don't think that is a good idea. Regards, That Jinja guy -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
