#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: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Carlton Gibson):
As maintainer of both django-filter and crispy forms, I'd say I (too) am
in favour of the `b` solution, i.e. adopting the proposal.
If we were writing new code, requiring an explicit template engine would
be fine, but we're seeing code that's been working fine — quite literally
— for years that's leading to the error here.
What's more it's only (≈) 1 user in a 100 that configures multiple
template engines so the point about it being an untested and surprising
edge-case is exactly right.
--
Ticket URL: <https://code.djangoproject.com/ticket/27359#comment:10>
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.63910fd8a7893f01a8545537cd18a820%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
