Hi Graham, if you are using relative templates with inheritance and/or includes you'll probably get the error. It seems somehow the URI of the inherited template already gets : replaced by $ (mako probably bet this) and then tries to render the template bypassing the conditional looking for not being abspath and containing a semi-colon.
For asset specs it's just personal preferences, I use a lot of templates not relative to the same root within the same project or across multiple packages and sometimes mix up mako-jinja2-chameleon, so that's a simple and well supported way to do it and it works with all supported template languages. The other way would be to provide all template paths to mako.directories but in that case won't support other template languages until you do the same for all of them. It's also the way to override assets so it makes sense to use the same way of specifying assets across my projects(s). It's not a global principle for all frameworks but I think it could be considered a good one for pyramid. On Saturday, 30 June 2012 09:40:04 UTC-4, Graham Higgins wrote: > > On Fri, 2012-06-29 at 06:56 -0700, Blaise Laflamme wrote: > > It's an already known problem and should be fixed for next version. > > Works for me when hand-added to 1.4dev. > > > However it's also a good habit to use asset spec, I personally prefer > > it over relative path most of the time. > > Could you explain a little more why the asset approach is a "good > habit"? It's specificity to Pyramid seems to run counter to re-use > principles. > > > -- > Graham Higgins > > http://bel-epa.com/gjh/ > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-discuss/-/HBZxvsPepgIJ. 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/pylons-discuss?hl=en.
