Yes, the problem is the one you're describing, if we find a way to
gather all involved modules when py:layout is being used then we just
need to change _get_extended_modules to reload all templates. :-)
Thanks for pointing this out.
Ciao
Michele
adsva wrote:
> Hi,
>
> I've noticed that when using kid layout templates (py:layout), they
> don't get autoreloaded. I tried to get to the bottom of this and can't
> really find a good solution. When using py:extend, the resulting
> template is made a subclass of the extended template class, which
> enables the autoreloader to find all reload candidates by looking at
> superclasses. But using layouts, the connection between the layout and
> the current template seems to get lost since the resulting template is
> made from a recursive _pull()-call, as can be seen in this example from
> a kid source using a layout template:
>
> def _pull(self):
> kw = dict(layout_params)
> kw.update(self.__dict__)
> kw.pop("assume_encoding", None)
> kw.pop("_layout_classes", None)
> temp = template_util.get_base_class('layout.kid', __file__)(**kw)
> temp._match_templates = self._match_templates +
> temp._match_templates
> return temp._pull()
>
> Am I missing something here? Is there a way to introspectively find out
> whether a template was made using layout templates?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" 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/turbogears
-~----------~----~----~----~------~----~------~--~---
