#9081: [patch] More flexible render_to_response()
---------------------------------------------+------------------------------
Reporter: bhagany | Owner: ccahoon
Status: new | Milestone:
Component: HTTP handling | Version: 1.0
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Comment (by bhagany):
Man, I am confused as to what 'Accepted' from a core committer means.
@ccahoon - it's true, the HttpResponse(render_to_string(..), ..) syntax is
pretty much exactly what render_to_response does. I guess I am confused
as to why render_to_response is there in the first place, if there's that
much decision/discussion to be had around something like this? I just
want a consistent, and easy way to render responses. render_to_response
is easier by a hair, but I can't get the consistency I need out of it.
That's the only reason for this patch.
--
Ticket URL: <http://code.djangoproject.com/ticket/9081#comment:8>
Django <http://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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
