It will never happen. (I'll buy everyone a round when I'm proven wrong) Regarding the Coffin issue. If you're using form.as_*, you're already doing something wrong (no offense). The rendering shortcuts are complete crap and offer no flexibility. As for it not supporting Django's mark_safe, it's possible that could be addressed, but most people don't seem to care. It's like choosing your database, you're not building your entire application to work on Oracle if you've chosen MySQL. Once you know how things work, you build for the purpose.
I for one would love to see Jinja replace Django's template language, but people are stubborn (as are we, about using Jinja). On Dec 13, 7:31 am, Jeff Bauer <[email protected]> wrote: > On 12/13/2010 08:25 AM, Ludvig Ericson wrote: > > > On 13 dec 2010, at 15:17, Jure Vrscaj wrote: > > >> My question is, are there any efforts on making Jinja2 the default > >> Django templating engine at some point? > > > Well, there is Coffin. > > >http://www.davidcramer.net/code/479/using-jinja2-with-django.html > > Things not supported by Coffin: "Django-type safe strings > passed through the context are not converted and therefore > not recognized by Jinja2. For example, a notable place were > this would occur is the HTML generation of Django Forms." > > Jeff Bauer > Rubicon, Inc. -- You received this message because you are subscribed to the Google Groups "pocoo-libs" 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/pocoo-libs?hl=en.
