Re: Passing RequestContext as dict vs. context_instance=RequestContext

[Jesaja Everling]

Hi Bruno,
Hi Alex,

thank you very much for your helpful responses.
I will do as you suggested and use RequestContext as it is supposed to
be used or via Alex' generic view trick.

Best Regards,

Jesaja Everling

On Feb 25, 3:27 pm, Alex Robbins 
wrote:
> If you get tired of forgetting to add theRequestContextyou can use
> direct_to_template[1] instead. (I almost always forget it the first
> time)
>
> It is almost exactly like render_to_response, you'd use it like this:
>
> def index(request):
>     return direct_to_template(request, 'index.html', {
>         'extra_context_var': value,
>         })
>
> Alex
>
> [1]http://docs.djangoproject.com/en/dev/ref/generic-views/#django-views-...
>
> On Feb 24, 6:00 am, Jesaja Everling  wrote:
>
> > Hi all!
>
> > Is there any difference between these two ways of using
> >RequestContext?
> > I'm asking because I usually use the first approach, but I want to
> > make sure that there are no subtle differences.
>
> > 1)
> > def index(request):
> >     return render_to_response('index.html',
> >                              RequestContext(request,
> >                                              {}
> >                                              ))
>
> > 2)
> > def index(request):
> >     return render_to_response('index.html',
> >                              {},
> >                              context_instance=
> >RequestContext(request))
>
> > Thanks!
>
> > Jesaja Everling

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Passing RequestContext as dict vs. context_instance=RequestContext

[Alex Robbins]

If you get tired of forgetting to add the RequestContext you can use
direct_to_template[1] instead. (I almost always forget it the first
time)

It is almost exactly like render_to_response, you'd use it like this:

def index(request):
return direct_to_template(request, 'index.html', {
'extra_context_var': value,
})

Alex

[1] 
http://docs.djangoproject.com/en/dev/ref/generic-views/#django-views-generic-simple-direct-to-template

On Feb 24, 6:00 am, Jesaja Everling  wrote:
> Hi all!
>
> Is there any difference between these two ways of using
> RequestContext?
> I'm asking because I usually use the first approach, but I want to
> make sure that there are no subtle differences.
>
> 1)
> def index(request):
>     return render_to_response('index.html',
>                               RequestContext(request,
>                                              {}
>                                              ))
>
> 2)
> def index(request):
>     return render_to_response('index.html',
>                              {},
>                               context_instance =
> RequestContext(request))
>
> Thanks!
>
> Jesaja Everling

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Passing RequestContext as dict vs. context_instance=RequestContext

[bruno desthuilliers]

In Feb 24, 1:00 pm, Jesaja Everling  wrote:
> Hi all!
>
> Is there any difference between these two ways of using
> RequestContext?
> I'm asking because I usually use the first approach, but I want to
> make sure that there are no subtle differences.
>
> 1)
> def index(request):
>     return render_to_response('index.html',
>                               RequestContext(request,
>                                              {}
>                                              ))


This actually work (at least it should), but it's a bit of a waste
since loader.render_to_string (which is called by render_to_response)
will build a Context object from the mapping (here a
RequestContext).


> 2)
> def index(request):
>     return render_to_response('index.html',
>                              {},
>                               context_instance =
> RequestContext(request))


This is the canonical way to call render_to_response. You should
switch to this one IMHO.

>From a quick glance at Django's source code, it shouldn't AFAICT make
any difference, except for the useless overhead of building a Context
object from the RequestContext instance. FWIW, one of the nice
features of OSS is that, well, it's open source - so if you find the
documentation unclear or lacking, you can access the most accurate and
up to date doc : the source code itself !-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Passing RequestContext as dict vs. context_instance=RequestContext

[Jesaja Everling]

Hi all!

Is there any difference between these two ways of using
RequestContext?
I'm asking because I usually use the first approach, but I want to
make sure that there are no subtle differences.

1)
def index(request):
return render_to_response('index.html',
  RequestContext(request,
 {}
 ))

2)
def index(request):
return render_to_response('index.html',
 {},
  context_instance =
RequestContext(request))

Thanks!

Jesaja Everling

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.