> Sure, just write a short wrapper function which calls > "render_to_response" and uses a RequestContext. One example which you > can use is available on djangosnippets: > > http://www.djangosnippets.org/snippets/3/
Ah, brilliant! Problem solved =D > Having Django "automatically" do this for you would be a bad idea, > because context processors may expose information to templates that > you wouldn't want to have globally available to template authors (for > example, the "request" context processor, because it makes the full > HttpRequest available, also necessarily makes things like the user's > session -- which is an attribute of the request -- and any posted data > available). Ok, I see and agree. Since all the templates of my application are under my control this aspect did not come into my mind :-) Maybe one could post a link to this snippet in the docs? I guess I wasn't the only one asking for another approach? 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 -~----------~----~----~----~------~----~------~--~---
