What I've found as a solution, though I don't know how much it is recommended as a programming practice is to have your variable defined in a "custom" request context and then use that request context instead of the default one.
You create you request context and based on the default context then just set it up in settings to be used for the whole site. You can star of on this link than expand to other sites: http://docs.djangoproject.com/en/dev/ref/templates/api/#writing-your-own-context-processors I'm still in the process of gathering all the information, and would like to see a response from a more experienced and versed py/django programmer on this matter. What's the trade off. I know it comes down to : "We're all conseting adults here" so don't do bad stuff or bad stuff will be done unto you. But still, is there any other concerns with this solution? hope this helps. On Wed, Mar 16, 2011 at 4:52 PM, Isaac XxX <vyrp...@gmail.com> wrote: > t (normally Requ -- 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.
