I remember this coming up on django-users and IRC once or twice, and never thought too much about it, but currently, template inheritance and includes don't work together at all:
* Blocks included in a parent template cannot be overwritten in a child template. * Blocks from an include in a child template cannot overwrite blocks in a parent template. Now that I was in a situation myself were this would have been handy, I wonder why that doesn't (shouldn't?) work: It turns out that changing ConstantIncudeNode to expose ``make self.template.nodelist`` as ``self.nodelist`` is all that is necessary (tests still pass). Granted, for dynamic includes it is probably harder or possibly even undoable (I haven't looked into that), but why not enable it for the presumable prevalent use case (static includes)? Am I overlooking something, or was there just no demand so far? Related tickets: #7321 (invalid), possibly: #6646 (design decision needed). Michael --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
