Adrian Holovaty wrote: > No, this isn't the case -- loaded template tags/filters aren't made > available in child templates. This happens on purpose, so that a child > template is less coupled to its parent template.
If you're extending a base template, aren't you already coupling the two? I could see an argument towards more flexibility where if you want it less coupled you don't put any "load"s in the base template. But if you don't care and want less repetition (DRY) of "load" statements, put it in the base template. There's probably other cases I'm not considering. Thanks, Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users -~----------~----~----~----~------~----~------~--~---
