I had similar problem when I was implementing Breve template engine renderer (http://github.com/momyc/pyramid-breve). The challenge was that I standard Pyramid technique of detecting calling package was failing because call stack was deeper than it usually is and that renderer library package was detected as application package.
Alex K I have not see what fix was made but I ended up by allowing developer to configure "default" package via renderer configuration since I could not find reliable way of doing it otherwise. On Saturday, December 28, 2013 7:04:07 PM UTC-4, Bert JW Regeer wrote: > > > On Dec 28, 2013, at 13:33, Mike Orr <[email protected] <javascript:>> > wrote: > > > I'm making a set of demo apps, which is a directory with several > > one-file Pyramid applications and a common template file they all use. > > So they are not in a named package. How do I specify the template in > > the 'renderer' argument (page.mako or page.pt, I'm not sure which I > > want to use)? With renderer="page.mako" I got a template not found > > error. > > > > Also, is there a debugging setting to tell me which paths it considered? > > > > -- > > Mike Orr <[email protected] <javascript:>> > > > > > Relative templates do not yet work in pyramid_mako. A fix has been landed > in master, but it is waiting on me to find some time to change it so that > it falls back to mako.directories if it exists so that it is more in line > with pyramid_jinja2. I am not sure what pyramid_chameleon does. > > Bert -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/groups/opt_out.
