Why not making RequestContext the default Context ?

2 views
Skip to first unread message

kahless

unread,
Jan 30, 2007, 2:24:41 PM1/30/07
to Django users
hi,

is there a reason why by default the render_to_response uses a Context
and not RequestContext ?
since it's the goal to make applications (and therefore templatetags &
co) as independent as possible (afaik) so it would be possible to
simply call templatetags from another application imho there should be
by default the request object in the context and a way to add
additional variables to the context (ie.
"TEMPLATE_CONTEXT_PROCESSORS")

i wonder if it wouldn't be better to have render_to_response by
default use a RequestContext, or make it configurable.. or... at least
add to the "Do's and Dont's for Application Writers"-page (http://
code.djangoproject.com/wiki/DosAndDontsForApplicationWriters) to
always pass a RequestContext into render_to_response.

or am i missing something important and it's not always a good idea to
use RequestContext ?


thanks & cu,
Herbert Poul

Reply all
Reply to author
Forward
0 new messages