#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
----------------------------------+--------------------------------------
Changes (by Raphael Das Gupta):
* status: closed => new
* resolution: needsinfo =>
Comment:
django-crispy-forms [https://github.com/django-crispy-forms/django-crispy-
forms/blob/884a28e08204ef49da8b53fd32a9d19d6de7f393/crispy_forms/layout.py#L400
seems to have the same problem] when used in a Django project that has
multiple template engines of the same backend configured. (I haven't yet
tried with multiple engines of different backends.)
What are libraries supposed to use instead of `Template('template content
here')`? By definition they cannot know what template engines the projects
that the library will be used in have configured.
--
Ticket URL: <https://code.djangoproject.com/ticket/27359#comment:7>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.30a386896e31cc35c919718e359691b9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
