#24168 closed Bug (fixed)
TemplateResponse and TemplateView cannot select a specific template engine
| Reported by: | Aymeric Augustin | Owned by: | nobody |
|---|---|---|---|
| Component: | Template system | Version: | dev |
| Severity: | Normal | Keywords: | multiple-template-engines 1.8 |
| Cc: | Zach Borboa | Triage Stage: | Ready for checkin |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
TemplateResponse should gain an engine argument.
TemplateResponseMixin should gain an engine attribute.
Change History (8)
comment:1 by , 11 years ago
| Cc: | added |
|---|
comment:2 by , 11 years ago
| Has patch: | set |
|---|---|
| Needs tests: | set |
| Triage Stage: | Unreviewed → Accepted |
comment:3 by , 11 years ago
| Needs tests: | unset |
|---|
comment:4 by , 11 years ago
While I was in the area, I added ShortcutTests.test_render_to_response_with_status which was missing from fdbfc98003f0ba2d3a12def63a75560791f3602d.
comment:5 by , 11 years ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
comment:6 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
https://github.com/django/django/pull/3992