Re: Contrib context processor?

[Ned Batchelder]

In my own context processor, I added 'settings' as the entire settings module.  Then I can get settings.WHATEVER in the templates.  This solved our problem of dribbling in individual settings as we needed them.  Any feelings about doing that in a standard context?  Then there is no slippery slope, as all of the settings are brought in at once. --Ned. James Bennett wrote: On 10/13/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote: I'm adding it locally, but was wondering if you'd like a patch for one either to core or contrib? It came up in ticket 2532, and Adrian vetoed it on the grounds that adding context processors for some settings could be a slippery slope toward having a context processor for every setting. -- Ned Batchelder, http://nedbatchelder.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers -~----------~----~----~----~------~----~------~--~---