On Oct 21, 4:26 am, "James Bennett" <[EMAIL PROTECTED]> wrote: > On Mon, Oct 20, 2008 at 9:30 PM, Chuck22 <[EMAIL PROTECTED]> wrote: > > Adding context_instance=RequestContext(request) to the method fixed > > the problem. Seems this should be done by default for > > render_to_response method. Thank you. > > It would be technically impossible to do this; render_to_response has > no knowledge of the HttpRequest object (which is required for a > RequestContext) unless you explicitly pass it as an argument.
True, but there's no reason that render_to_response couldn't just take 'request' as its third parameter, using a RequestContext if it is provided, rather than the unnecessarily verbose context_instance stuff. In fact at work we have written a shortcut to do just this. -- DR. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
