I see benefit on having it by default as users using jinja2 may expect the filters as their are told by the jinja2 documentation, others may probably argue on having it as an optional feature or even having a way to turn it off just in case you need a clean setup, probably my patch is too naive, it does not handle conflicts, such as having the developer override on of the default functions, tough that could be solved easily (adding the build-ins first then overriding with the developer given filters).
I think we are speculating much, as I feel the jinja2 turbogears users are very few and there is not a lot of feedback on what the potential users would like or work for them. Regards, Carlos Ruvalcaba -- 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.
