#24168: TemplateResponse and TemplateView cannot select a specific template
engine
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: closed
Component: Template system | Version: master
Severity: Normal | Resolution: fixed
Keywords: multiple-template- | Triage Stage: Ready for
engines 1.8 | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Aymeric Augustin <aymeric.augustin@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"2133f3157eff853329bafb7fda74c3c8fb4eae42"]:
{{{
#!CommitTicketReference repository=""
revision="2133f3157eff853329bafb7fda74c3c8fb4eae42"
Fixed #24168 -- Allowed selecting a template engine in a few APIs.
Specifically in rendering shortcuts, template responses, and class-based
views that return template responses.
Also added a test for render_to_response(status=...) which was missing
from fdbfc980.
Thanks Tim and Carl for the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24168#comment:6>
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/067.898338aa7a086d50f862a64d336a58a4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
