Hey Vincent, Create a ticket on Github if you would please, and I will take a look at it. It looks like it would be fairly simple to add :-).
Cheers, Bert On Apr 7, 2014, at 03:49 , Vincent Férotin <vincent.fero...@gmail.com> wrote: > Hi, Pyramid's developers and Bert! > > Developing a Pyramid application with Mako as template engine, > I wonder if it could be pertinent to add a new configuration value > to Mako's binding, to allow settings 'future_imports' > ( > http://docs.makotemplates.org/en/latest/usage.html#mako.template.Template.params.future_imports > ). > This argument for mako.template.Template and mako.lookup.TemplateLookup > is new as of Mako 0.8 ( > http://docs.makotemplates.org/en/latest/changelog.html#change-b7ef07a547af42dd2677a0ee710a88d8 > ). > > For my personal usage, I'd like using such a feature for directly using > Unicode string literals in templates, > and so ensuring my application equally works on Python 2 and 3, especially 3.2 > (instead of waiting for 3.3 with PEP 414). > > What do you guys think about? > Will I open a new issue on pyramid_mako's GitHub? > > -- Vincent > > -- > You received this message because you are subscribed to the Google Groups > "pylons-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pylons-devel+unsubscr...@googlegroups.com. > To post to this group, send email to pylons-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/pylons-devel. > For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME cryptographic signature
