> I'll have to disagree with you here. I think this is a perfect > example of Russ's point. Somewhere on your PYTHONPATH just write a > function that looks something like this (warning, untested code): > > from django.shortcuts import render_to_response as old_rtr > from django.template import RequestContext > def render_response(request, *args, **kwargs): > kwargs['context_instance'] = RequestContext(request) > return old_rtr(*args, **kwargs) > > Now all you have to is import your new render_response method and use > that instead of the default render_to_response.
Very cool. I must admit I quite like the flexibility of python's import statements. I'll give this a try tomorrow but at first glance it looks quite flexible. The one catch that I see is that you still have to go through all your views and make sure that you're now passing in a request object, and if you miss any then you won't necessarily know until you notice that your page is rendered funny. On the other hand, the proposal I put out there earlier didn't really solve this problem either. Thanks for the tip! Mike --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
