On 1/12/06, Jeremy Jones <[EMAIL PROTECTED]> wrote: > Mine would do the same thing. I didn't go to the drastic measures of > wiping my TG related eggs, though. Mine is working great on everything > but the few straggling pages that extend master.kid. Every time I get > the error on a page, I just take out the py:extends="master.kid" (or > whatever the syntax is) and manually put the pertinent stuff in the > page. It's a pain, I know, but I have not yet had a single error on a > non-extended page. I would not consider this a long-term, workaround, > though. I think this needs to be confidently fixed.
py;extends="'master.kid'" functions very differently from py:extends="sitetemplate" (the single quotes have Kid go hunting around for the template, whereas the sitetemplate way without the quotes refers directly to a module available in your template module's namespace). So, maybe there does remain some issue there. Kevin
