Hi!
> Look at TEMPLATE_CONTEXT_PROCESSORS and use RequestContext instead of
> Context in your views. See [1] for lots of details. Remember to read the
> note about to pass RequestContext to render_to_response().
You mean like this:
return render_to_response('my_template.html',
my_data_dictionary,
context_instance=RequestContext(request))
I can see why it is necessary to instantiate RequestContext with the
request object. But in terms of DRY I wonder wether there isn't a
better way? I haven't looked at the sources yet so I cannot say what
is possible and what not.
Maybe RequestContext could be a member of the request object so that
the caller of the view method would be responsible for instantiating
the RequestContext. Just an idea :-)
Yours,
Lars
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
