Switching the default template system would have a disruptive change on the Django ecosystem. For example, contrib.admin doesn't provide Jinja2 templates. I imagine there are third-party apps in the same situation.
Here's a past thread about the same proposal: https://groups.google.com/d/topic/django-developers/Bk-22bKqCTo/discussion On Friday, January 26, 2018 at 7:31:30 AM UTC-5, Ander Ustarroz wrote: > > I have been working a lot with Django and I have always asked myself how > is it possible that they decided to use Django Template system rather than > Jinja2 <http://jinja.pocoo.org/docs/2.10/faq/>, when it is way more > intuitive, just like writing natural Python! Someone may argue that it's > matter of taste but I bet they haven't tried both template systems. > > Yeah I know... we can still use Jinja2 if we want to, but shouldn't it be > the native choice when is obviously the best? > > Regards > -- 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+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/6e0734cb-ae26-4633-b90b-0f3065766833%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
