OK, I actually thought I had rolled this back out. So, so that's my fault.
But my larger problem is that the hoops you have to go through to change the template engine are both unnecessary, and cumbersome. I would like changing the default template engine to be 1 line of very obvious code. Is there some reason we care about the order of the list of template engines, other than to set the default? It seems like the group of available template engines, and the one you want to be default are to seprate ideas. So, I would be all for moving this to environment.py but I would like to see it easier to change default template engines. --Mark On Dec 11, 2007 10:32 PM, Mike Orr <[EMAIL PROTECTED]> wrote: > > My Python-dev app includes the following in development.ini: > > # If you'd like to change the default template engine used to render text/html > # content in decorator style controllers, edit this line. > template_engine.default = genshi > > This can easily confuse the majority of users who don't use > decorator-style controllers and may not understand what they are. > It's doubly confusing that Genshi is the default for decorator > controllers while Mako is the default for ordinary controllers. Not > to mention that Genshi is not a Pylons dependency. > > Does it even make sense to set the template engine in the config file? > It's really a programming choice, not a deployment choice. Unless > the developer has provided a complete set of redundant templates for > the alternate engine (which nobody will do), the user cannot switch > the default engine without breaking the application. It's not like > swiching a SQLAlchemy backend. Changing the template engine requires > programming changes in the application. So it belongs more in > environment.py than the config file. > > -- > Mike Orr <[EMAIL PROTECTED]> > > > > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" 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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
