On Sun, Feb 16, 2014 at 1:12 AM, Donald Stufft <[email protected]> wrote:
> > On Feb 15, 2014, at 11:43 AM, Christopher Medrela <[email protected]> > wrote: > > My last post was pretty long and the most important questions and > statements > have left unanswered, so I will repeat them. > > What I'm proposing now is more conservative proposal. Firstly, Django will > support Jinja2 out-of-the-box, but DTL will remain the "blessed" option. > Secondly, Django will allow to mix DTL and Jinja2 templates (so you can > include/inherit DTL template from Jinja2 one and vice versa). > > After doing it, I could focus on 3) decoupling DTL or/and 4) rewriting > Django > builtin templates in Jinja2 or/and 5) moving rendering form widgets from > Python code to Jinja2 templates. > > After that all, we could start again the war DTL vs Jinja2, but please > focus > on the new proposal now. > > Questions are: > > 1) What do you think about the new proposal? Would it be useful? > > 2) Jinja2 doesn't support 3.2. Will Django 1.8 support 3.2? > > 3) Supporting Jinja2 out-of-the-box means introducing dependencies. Are we > ready for this? > > > If we have Jinja2 I don't see any reason to keep the DTL as the blessed > option. > Amongst other reasons: a) Some of us prefer DTL to Jinja2 :-) b) The Python3 support issue is a lingering concern c) There is a lot of legacy code and tutorials that need to continue to work as is. This is an area where there is a lot of benefit to moving slowly, IMHO. We're talking about a major part of the Django experience; Introducing a new option *and* switching to it in a single release sounds like a recipe for confusion to me. As I see it, there are three possible options here: 1) Add Jinja2 as a supported option, but stick with DTL as the default. 2) Add Jinja2 as a supported option, and indicate that long term, we're going to switch to Jinja as the default 3) Add Jinja2 as a supported option and move to it immediately as the default. My personal preferences would be in that order. This is something where historically, we would have gone to the BDFLs for a call; I suspect the core team might need to have a quick discussion and make a call, lest this turn into the mother of all bike sheds. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq849aJXA-H8syt8G4evKz3yXpgD2h93bC45rt0BYdv2%2BQkQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
