I've been trying to figure out how to use a custom subclased RequestContext[1] object in my generic views. Looking at the code of django/views/generic/*.py it looks like this class is hard-coded in each of the views.
Ideally, I'd be able to set something in the settings.py to specify my default RequestContext class, but I don't readily see a way to go about that short of hacking the django.templates.context module. Another alternative might be monkey-patching django.templates.context to include my own subclass as RequestContext, though again, this is an ugly hack. Any pointers/guidelines/best-practices on how to coerce generic-views into using a custom RequestContext object would be much appreciated. -tim [1] stemming from helpful suggestions by Marty & Doug here http://groups.google.com/group/django-users/browse_thread/thread/8cfd4b882389812 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
