.mak is also what TW uses, so there might be some historical justification for using .mak
I personally +1 the effort to move over to .mako, and could/would make the change in TW to match. cheers. -chris On May 14, 10:27 pm, Jorge Vargas <[email protected]> wrote: > On Wed, May 13, 2009 at 3:00 AM, Seth <[email protected]> wrote: > > > I've been lurking in the #turbogears channel from time-to-time and > > have observed some discussion of whether future TG releases should > > have genshi or mako set as the default templating engine. > > > Having never tried Mako in a TG setting, I decided to fire up a new TG > > 2 test app to mess around with TG+Mako. I had the hardest time, > > however, figuring out why TG wouldn't load my *.mako templates; until > > I saw a post somewhere stating that TG uses ".mak" as its Mako > > extension, not .mako. > > This is a bug/anti-feature of TW and the very old Buffet stuff. To be > honest I don't remember why anymore. > > IMO they should be switch to .mako they just need someone to do the > work. But it needs to be fixed in TW and TG. > > > Weird. Why is this? Is there a simple config variable somewhere to > > make it load *.mako instead? (yes I'm lazy and would rather keep the > > same file extension for my pylons and tg mako templates) > > no, there is no config. .mak shouldn't be anyway. > > > Also on a side note: I've noticed that the default TG 2 setup.py's > > "message_extractors" line looks like it's matching '*.mako'. Is this a > > bug? > > Most likely. But the bug is .mak > > > Thanks, > > Seth --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
