Hi, You do have a couple of options, as mentioned by others earlier. One of them is creating a base callable class view for your entire site and have it subclassed for specific cases, but I think that would be a bit heavy to work with here. Keep in mind that's entirely possible, but you might find yourself writing more code just to make everything work (with inheritance and all), unless it really fits your need. Also, you could subclass the Context class itself, which I think could be a nice option if you do include the same template variable over and over and cannot put them in a context_processor.
Check out that example : http://dpaste.com/hold/22238/ As you know, adding more and more reusable variables would only be a matter of trivial subclassing. Oh, and BTW, if you do need context_processors, you should subclass RequestContext instead of Context. --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
