Nathaniel Whiteinge said the following:
> Either way, this is a bike-shed issue.
In fact, he can simply do this:
from django.views.generic.simple import direct_to_template as render_response
and get the name he wants without patching anything :)
--
Collin Grady
For the record, this issue really bothered me too until I found
direct_to_template. Now it is a non-issue.
On Jun 11, 1:22 pm, Gabriel Farrell <[EMAIL PROTECTED]> wrote:
> It's fairly clear that we're setting
> up a dictionary of variables for the template, pulling data from the
> Profile model.
On Jun 10, 5:44 pm, "Rajeev J Sebastian" <[EMAIL PROTECTED]>
wrote:
> On Tue, Jun 10, 2008 at 11:20 PM, Gabriel Sean Farrell <[EMAIL PROTECTED]>
> wrote:
>
> > direct_to_template, I'd rather avoid abusing a function by ignoring
> > its name and exercising largely undocumented functionality.
On Tue, Jun 10, 2008 at 11:20 PM, Gabriel Sean Farrell <[EMAIL PROTECTED]>
wrote:
> direct_to_template, I'd rather avoid abusing a function by ignoring
> its name and exercising largely undocumented functionality. After
> all, my params aren't going directly to the template.
Calling a generic
In response to http://fi.am/entry/shortcutting-render_to_response/ --
posting it here rather than some little comment box.
PART 1: A Bold Diff
---
In regard to the clumsiness of render_to_response and RequestContext,
I too like the solution at
