I got the answer on IRC that this is not a bug as explained in the documentation for include https://docs.djangoproject.com/en/1.8/ref/templates/builtins/#include
Suriya On Thursday, September 10, 2015 at 2:55:42 PM UTC+5:30, Suriya Subramanian wrote: > > Hi, > > I think there is a bug in how 'block' and 'include' template tags interact > in the Django Template Language. I have created a Gist showing this issue: > https://gist.github.com/anonymous/2627bb35955db77dbfaa > > The order of the files in the Gist can be a bit confusing. I will explain > what I am trying to do here. I have a base template that defines two > blocks, one block directly, and one block within an included file. A child > template extends the base template and defines both the blocks. However, in > the rendered output the child is able to override only of the blocks. The > child template is unable to override the block defined in the include file. > > My understand is that, a file and block included within a parent template > should be considered a part of the parent. However, that does not seem to > be the case. > > Thanks, > Suriya > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/5ee79ae1-9d6f-41de-aa23-369d3104e455%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
