Ticket #6793: exported_settings_processor.diff

django/conf/global_settings.py

@@ -156 +156 @@
     'django.core.context_processors.debug',
     'django.core.context_processors.i18n',
     'django.core.context_processors.media',
+    'django.core.context_processors.exported_settings',
 #    'django.core.context_processors.request',
 )
 

django/core/context_processors.py

@@ -60 +60 @@
 def request(request):
     return {'request': request}
 
+def exported_settings(request):
+    context_extras = {}
+    e = getattr(settings, 'EXPORTED', None)
+    if not e:
+        return context_extras
+
+    for field in e.fields:
+        context_extras[field[0]] = field[1]
+    return context_extras
+
 # PermWrapper and PermLookupDict proxy the permissions system into objects that
 # the template system can understand.
 

docs/settings.txt

@@ -138 +138 @@
 
 The only place you should assign to settings is in a settings file.
 
+Using settings in templates
+===========================
+
+Define a class called EXPORTED with the fields attribute set
+to an iterable of pairs. The first component is the template
+variable name, and the second is the value. For example:
+
+    class EXPORTED:
+        fields = ( ('foo', 'bar'), ('images_url', MEDIA_URL + '/images/'))
+
+Note that this feature depends on RequestContext. 
+See the `RequestContext docs`_ for more information.
+
+.. _RequestContext docs: ../templates_python/#subclassing-context-requestcontext
+
 Security
 ========
 
@@ -907 +922 @@
     ("django.core.context_processors.auth",
     "django.core.context_processors.debug",
     "django.core.context_processors.i18n",
-    "django.core.context_processors.media")
+    "django.core.context_processors.media",
+    "django.core.context_processors.exported_settings")
 
 A tuple of callables that are used to populate the context in ``RequestContext``.
 These callables take a request object as their argument and return a dictionary