#27359: Make it possible to specify a default template engine
     Reporter:  Artur Barseghyan  |                    Owner:  nobody
         Type:  New feature       |                   Status:  new
    Component:  Template system   |                  Version:  1.8
     Severity:  Normal            |               Resolution:
     Keywords:  template engines  |             Triage Stage:  Unreviewed
    Has patch:  0                 |      Needs documentation:  0
  Needs tests:  0                 |  Patch needs improvement:  0
Easy pickings:  0                 |                    UI/UX:  0

Comment (by Aymeric Augustin):

 Right, this situation is described in this part of the documentation:
 (the first two paragraphs).

 I suppose the transition could be smoothed by adopting a convention for
 determining the default Django templates engine, perhaps by deciding it
 the one called "django" (or similar) when there are multiple engines

 Can you start by reporting this issue to `django-cms`? They're doing
 `context.template = Template('')` which, per the current documentation,
 isn't supported.

Ticket URL: <https://code.djangoproject.com/ticket/27359#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to