Opened 8 years ago
Closed 8 years ago
#25929 closed Bug (invalid)
render_to_response with RequestContext problem
| Reported by: | Hugo Tácito | Owned by: | nobody |
|---|---|---|---|
| Component: | Utilities | Version: | 1.9 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
In django 1.9, I am unable to use render_to_response with RequestContext without any deprecation warning, I need to use RequestContext because of the context_processors... Why not add the parameter request to render_to_response and pass it to render_to_string to solve this issue? For now, the only way I have to do this is calling:
HttpResponse(render_to_string(template, dict_context, request=request))
Change History (2)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Sorry, I completely forgot about render from shortcuts, I'm gonna close this...
Note:
See TracTickets
for help on using tickets.
Could you clarify why
render(request, template, dict_context)doesn't do what you want?