This is greatly needed. Thanks for taking this on.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsu
On 2 oct. 2014, at 14:35, Josh Smeaton wrote:
> - The pluggable solution works well when you have a common interface, but a
> different implementation in the backend. Have you thought about how to
> support differences in syntax (interface) between various templating
> libraries?
Yes, I have.
Nice! I've thought about trying to tackle this myself, but never got past
the thinking stage. Thanks for taking this on Aymeric. I've got a couple of
technical/design questions.
> I’ve been thinking about providing built-in support for Jinja2 in Django.
I found that support
> On Thu, Oct 2, 2014 at 3:04 AM, Aymeric Augustin > polytechnique.org> wrote:
>>
>>> Hello,
>>>
>>> I've been thinking about providing built-in support for Jinja2 in
>>> Django. I found that supporting pluggable template engines, like Django
>>&g
wrote:
>
>
> On Thu, Oct 2, 2014 at 3:04 AM, Aymeric Augustin <
> aymeric@polytechnique.org > wrote:
>
>> Hello,
>>
>> I've been thinking about providing built-in support for Jinja2 in Django.
>> I found that supporting pluggable template engines, like D
On Thu, Oct 2, 2014 at 3:04 AM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> Hello,
>
> I've been thinking about providing built-in support for Jinja2 in Django.
> I found that supporting pluggable template engines, like Django does for
> databases,
Hello,
I've been thinking about providing built-in support for Jinja2 in Django. I
found that supporting pluggable template engines, like Django does for
databases, caches, etc. would be the most elegant solution. The best summary I
have at this time is on the crowdfunding campaign&#
