On Feb 16, 2007, at 9:05 PM, Cliff Wells wrote:
> Actually, the "TG spec" is completely superfluous. You can use "/"
> rather than "." and it will work just fine. I just removed support
> for
> dotted path notation from Breve as it causes problems (e.g. paths with
> dots in them) and provides nothing in return. If you don't have a
> large
> userbase of people expecting dot notation to work, I'd get rid of
> it now
> before you do.
I tried to remove the '.' handling stuff from my Buffet.... no luck.
Here's the logic performed for all engines except Myghty/Mako:
if not engine_name.startswith('pylons') and not \
engine_name.startswith('mako'):
full_path = os.path.join(engine_config['root'],
template_name)
full_path = full_path.replace(os.path.sep,
'.').lstrip('.')
If I remove that, the Kid test fails. Apparently it needs the '.'
replaced with a '/' and needs the engine's root added. This logic is
carried over from the stand-alone Buffet package. I'm not entirely
sure why Kid and the other engines need this logic performed to
handle the dot notation but they seem to require it.
If someone else who knows more about the Buffet/Template plugin stuff
could shed some light on this, I'm all ears. :)
Cheers,
Ben
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" 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/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
