blocks|key|1439173|text|如果使用Django内置的通用视图或在render_to_response快捷方式函数中传入上下文实例关键字参数，django提供对模板的某些常用设置常量的访问，比如settings.MEDIA_URL和一些语言设置。下面是每种情况的一个示例：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1439174|from+django.shortcuts+import+render_to_response
from+django.template+import+RequestContext
from+django.views.generic.simple+import+direct_to_template

def+my_generic_view(request,+template='my_template.html'):
++++return+direct_to_template(request,+template)

def+more_custom_view(request,+template='my_template.html'):
++++return+render_to_response(template,+{},+context_instance=RequestContext(request))|code-block|syntax|javascript|1439175|这两个视图都有几个常用的设置，如作为{{+MEDIA_URL+}}提供给模板的settings.MEDIA_URL等。|1439176|如果您希望访问设置中的其他常量，则只需解压缩您想要的常量并将它们添加到您在视图函数中使用的上下文字典中，如下所示：|1439177|from+django.conf+import+settings
from+django.shortcuts+import+render_to_response

def+my_view_function(request,+template='my_template.html'):
++++context+=+{'favorite_color':+settings.FAVORITE_COLOR}
++++return+render_to_response(template,+context)|1439178|现在您可以在模板上以{{+favorite_color+}}的身份访问settings.FAVORITE_COLOR。|1439179|entityMap^0|J|I|2B|I|0|0|I|F|13|I|0|0|0|A|K|Z|N|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|15|8|@]|D|@]|E|$]]|$1|O|3|P|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|Q|3|R|5|6|7|17|8|@$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|T|$]]

Django provides access to certain, frequently-used settings constants to the template such as <code>settings.MEDIA_URL</code> and some of the language settings if you use django's built in generic views or pass in a context instance keyword argument in the <code>render_to_response</code> shortcut function. Here's an example of each case:

<pre><code>from django.shortcuts import render_to_response
from django.template import RequestContext
from django.views.generic.simple import direct_to_template

def my_generic_view(request, template='my_template.html'):
 return direct_to_template(request, template)

def more_custom_view(request, template='my_template.html'):
 return render_to_response(template, {}, context_instance=RequestContext(request))
</code></pre>

These views will both have several frequently used settings like <code>settings.MEDIA_URL</code> available to the template as <code>{{ MEDIA_URL }}</code>, etc.

If you're looking for access to other constants in the settings, then simply unpack the constants you want and add them to the context dictionary you're using in your view function, like so:

<pre><code>from django.conf import settings
from django.shortcuts import render_to_response

def my_view_function(request, template='my_template.html'):
 context = {'favorite_color': settings.FAVORITE_COLOR}
 return render_to_response(template, context)
</code></pre>

Now you can access <code>settings.FAVORITE_COLOR</code> on your template as <code>{{ favorite_color }}</code>.

blocks|key|1653878|text|另一种方法是创建自定义模板标记，它可以让您从设置中钓鱼值。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1653879|@register.tag
def+value_from_settings(parser,+token):
++++try:
++++++++#+split_contents()+knows+not+to+split+quoted+strings.
++++++++tag_name,+var+=+token.split_contents()
++++except+ValueError:
++++++++raise+template.TemplateSyntaxError,+"%25r+tag+requires+a+single+argument"+%25+token.contents.split()[0]
++++return+ValueFromSettings(var)

class+ValueFromSettings(template.Node):
++++def+__init__(self,+var):
++++++++self.arg+=+template.Variable(var)
++++def+render(self,+context):++++++++
++++++++return+settings.__getattr__(str(self.arg))|code-block|syntax|javascript|1653880|然后，您可以使用：|1653881|{%25+value_from_settings+"FQDN"+%25}|1653882|在任何页面上打印它，而不需要跳过上下文处理器的限制。|1653883|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Another way to do this is to create a custom template tag which can let you fish values out of the settings.

<pre><code>@register.tag
def value_from_settings(parser, token):
 try:
 # split_contents() knows not to split quoted strings.
 tag_name, var = token.split_contents()
 except ValueError:
 raise template.TemplateSyntaxError, "%r tag requires a single argument" % token.contents.split()[0]
 return ValueFromSettings(var)

class ValueFromSettings(template.Node):
 def __init__(self, var):
 self.arg = template.Variable(var)
 def render(self, context): 
 return settings.__getattr__(str(self.arg))
</code></pre>

You can then use:

<pre><code>{% value_from_settings "FQDN" %}
</code></pre>

to print it on any page, without jumping through context-processor hoops.

blocks|key|1439246|text|上面来自bchhun的例子很不错，除了你需要显式地从settings.py构建你的上下文字典。下面是一个未经测试的示例，说明如何从settings.py的所有大写属性自动构建上下文字典(re："%5EA-Z0-9_%2B$")。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1439247|在settings.py的末尾：|1439248|_context+=+{}+
local_context+=+locals()
for+(k,v)+in+local_context.items():
++++if+re.search('%5E[A-Z0-9_]%2B$',k):
++++++++_context[k]+=+str(v)

def+settings_context(context):
++++return+_context

TEMPLATE_CONTEXT_PROCESSORS+=+(
...
'myproject.settings.settings_context',
...
)|code-block|syntax|javascript|1439249|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

The example above from bchhun is nice except that you need to explicitly build your context dictionary from settings.py. Below is an UNTESTED example of how you could auto-build the context dictionary from all upper-case attributes of settings.py (re: "^[A-Z0-9_]+$").

At the end of settings.py:

<pre><code>_context = {} 
local_context = locals()
for (k,v) in local_context.items():
 if re.search('^[A-Z0-9_]+$',k):
 _context[k] = str(v)

def settings_context(context):
 return _context

TEMPLATE_CONTEXT_PROCESSORS = (
...
'myproject.settings.settings_context',
...
)
</code></pre>

blocks|key|1439303|text|我稍微改进了一下chrisdew's+answer+(创建你自己的标签)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1439304|首先，创建文件yourapp/templatetags/value_from_settings.py，在其中定义您自己的新标记value_from_settings|style|CODE|1439305|from+django.template+import+TemplateSyntaxError,+Variable,+Node,+Variable,+Library
from+yourapp+import+settings

register+=+Library()
#+I+found+some+tricks+in+URLNode+and+url+from+defaulttags.py:
#+https://code.djangoproject.com/browser/django/trunk/django/template/defaulttags.py
@register.tag
def+value_from_settings(parser,+token):
++bits+=+token.split_contents()
++if+len(bits)+<+2:
++++raise+TemplateSyntaxError("'%25s'+takes+at+least+one+"+\
++++++"argument+(settings+constant+to+retrieve)"+%25+bits[0])
++settingsvar+=+bits[1]
++settingsvar+=+settingsvar[1:-1]+if+settingsvar[0]+==+'"'+else+settingsvar
++asvar+=+None
++bits+=+bits[2:]
++if+len(bits)+>=+2+and+bits[-2]+==+'as':
++++asvar+=+bits[-1]
++++bits+=+bits[:-2]
++if+len(bits):
++++raise+TemplateSyntaxError("'value_from_settings'+didn't+recognise+"+\
++++++"the+arguments+'%25s'"+%25+",+".join(bits))
++return+ValueFromSettings(settingsvar,+asvar)

class+ValueFromSettings(Node):
++def+__init__(self,+settingsvar,+asvar):
++++self.arg+=+Variable(settingsvar)
++++self.asvar+=+asvar
++def+render(self,+context):
++++ret_val+=+getattr(settings,str(self.arg))
++++if+self.asvar:
++++++context[self.asvar]+=+ret_val
++++++return+''
++++else:
++++++return+ret_val|code-block|syntax|javascript|1439306|您可以通过以下方式在模板中使用此标记：|1439307|{%25+load+value_from_settings+%25}
[...]
{%25+value_from_settings+"FQDN"+%25}|1439308|或via|1439309|{%25+load+value_from_settings+%25}
[...]
{%25+value_from_settings+"FQDN"+as+my_fqdn+%25}|1439310|as+...表示法的优点是，这使得通过简单的{{my_fqdn}}在blocktrans块中使用它变得很容易。|1439311|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/433162/can-i-access-constants-in-settings-py-from-templates-in-django/5235614#5235614^0|8|H|0|0|7|17|1R|J|0|0|0|0|0|0|0|6|M|B|Y|A|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@$A|19|B|1A|F|G]|$A|1B|B|1C|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|1D|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1E|8|@]|9|@]|C|$]]|$1|O|3|P|5|J|7|1F|8|@]|9|@]|C|$K|L]]|$1|Q|3|R|5|6|7|1G|8|@]|9|@]|C|$]]|$1|S|3|T|5|J|7|1H|8|@]|9|@]|C|$K|L]]|$1|U|3|V|5|6|7|1I|8|@$A|1J|B|1K|F|G]|$A|1L|B|1M|F|G]|$A|1N|B|1O|F|G]]|9|@]|C|$]]|$1|W|3|-4|5|6|7|1P|8|@]|9|@]|C|$]]]|X|$Y|$5|Z|10|11|C|$12|13]]]]

I improved <a href="https://stackoverflow.com/questions/433162/can-i-access-constants-in-settings-py-from-templates-in-django/5235614#5235614">chrisdew's answer</a> (to create your own tag) a little bit.

First, create the file <code>yourapp/templatetags/value_from_settings.py</code> in which you define your own new tag <code>value_from_settings</code>:

<pre><code>from django.template import TemplateSyntaxError, Variable, Node, Variable, Library
from yourapp import settings

register = Library()
# I found some tricks in URLNode and url from defaulttags.py:
# https://code.djangoproject.com/browser/django/trunk/django/template/defaulttags.py
@register.tag
def value_from_settings(parser, token):
 bits = token.split_contents()
 if len(bits) &lt; 2:
 raise TemplateSyntaxError("'%s' takes at least one " \
 "argument (settings constant to retrieve)" % bits[0])
 settingsvar = bits[1]
 settingsvar = settingsvar[1:-1] if settingsvar[0] == '"' else settingsvar
 asvar = None
 bits = bits[2:]
 if len(bits) &gt;= 2 and bits[-2] == 'as':
 asvar = bits[-1]
 bits = bits[:-2]
 if len(bits):
 raise TemplateSyntaxError("'value_from_settings' didn't recognise " \
 "the arguments '%s'" % ", ".join(bits))
 return ValueFromSettings(settingsvar, asvar)

class ValueFromSettings(Node):
 def __init__(self, settingsvar, asvar):
 self.arg = Variable(settingsvar)
 self.asvar = asvar
 def render(self, context):
 ret_val = getattr(settings,str(self.arg))
 if self.asvar:
 context[self.asvar] = ret_val
 return ''
 else:
 return ret_val
</code></pre>

You can use this tag in your Template via:

<pre><code>{% load value_from_settings %}
[...]
{% value_from_settings "FQDN" %}
</code></pre>

or via

<pre><code>{% load value_from_settings %}
[...]
{% value_from_settings "FQDN" as my_fqdn %}
</code></pre>

The advantage of the <code>as ...</code> notation is that this makes it easy to use in <code>blocktrans</code> blocks via a simple <code>{{my_fqdn}}</code>.

blocks|key|1439346|text|我发现最简单的方法是使用单个custom+template+tag|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1439347|from+django+import+template
from+django.conf+import+settings

register+=+template.Library()

#+settings+value
@register.simple_tag
def+settings_value(name):
++++return+getattr(settings,+name,+"")|code-block|syntax|javascript|1439348|用法：|1439349|{%25+settings_value+"LANGUAGE_CODE"+%25}|1439350|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.djangoproject.com/en/stable/howto/custom-template-tags/^0|E|J|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|10|8|@]|9|@]|C|$G|H]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

I find the simplest approach being a single <a href="https://docs.djangoproject.com/en/stable/howto/custom-template-tags/" rel="noreferrer">custom template tag</a>:
<pre><code>from django import template
from django.conf import settings

register = template.Library()

# settings value
@register.simple_tag
def settings_value(name):
 return getattr(settings, name, &quot;&quot;)
</code></pre>
Usage:
<pre><code>{% settings_value &quot;LANGUAGE_CODE&quot; %}
</code></pre>

blocks|key|1654107|text|IanSR和bchhun都建议在设置中覆盖TEMPLATE_CONTEXT_PROCESSORS。请注意，此设置有一个默认值，如果您在不重新设置默认值的情况下覆盖它，可能会导致一些奇怪的事情。在Django的最新版本中，默认设置也发生了变化。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1654108|https://docs.djangoproject.com/en/1.3/ref/settings/#template-context-processors|offset|length|1654109|默认TEMPLATE_CONTEXT_PROCESSORS：|1654110|TEMPLATE_CONTEXT_PROCESSORS+=+("django.contrib.auth.context_processors.auth",
"django.core.context_processors.debug",
"django.core.context_processors.i18n",
"django.core.context_processors.media",
"django.core.context_processors.static",
"django.contrib.messages.context_processors.messages")|code-block|syntax|javascript|1654111|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|27|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|Z|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|C]]]]

Both IanSR and bchhun suggested overriding TEMPLATE_CONTEXT_PROCESSORS in the settings. Be aware that this setting has a default that can cause some screwy things if you override it without re-setting the defaults. The defaults have also changed in recent versions of Django.

<a href="https://docs.djangoproject.com/en/1.3/ref/settings/#template-context-processors" rel="nofollow">https://docs.djangoproject.com/en/1.3/ref/settings/#template-context-processors</a>

The default TEMPLATE_CONTEXT_PROCESSORS :

<pre><code>TEMPLATE_CONTEXT_PROCESSORS = ("django.contrib.auth.context_processors.auth",
"django.core.context_processors.debug",
"django.core.context_processors.i18n",
"django.core.context_processors.media",
"django.core.context_processors.static",
"django.contrib.messages.context_processors.messages")
</code></pre>

blocks|key|1654141|text|如果使用基于类的视图：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1654142|#
#+in+settings.py
#
YOUR_CUSTOM_SETTING+=+'some+value'

#
#+in+views.py
#
from+django.conf+import+settings+#for+getting+settings+vars

class+YourView(DetailView):+#assuming+DetailView;+whatever+though

++++#+...

++++def+get_context_data(self,+**kwargs):

++++++++context+=+super(YourView,+self).get_context_data(**kwargs)
++++++++context['YOUR_CUSTOM_SETTING']+=+settings.YOUR_CUSTOM_SETTING

++++++++return+context

#
#+in+your_template.html,+reference+the+setting+like+any+other+context+variable
#
{{+YOUR_CUSTOM_SETTING+}}|code-block|syntax|javascript|1654143|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If using a class-based view:

<pre><code>#
# in settings.py
#
YOUR_CUSTOM_SETTING = 'some value'

#
# in views.py
#
from django.conf import settings #for getting settings vars

class YourView(DetailView): #assuming DetailView; whatever though

 # ...

 def get_context_data(self, **kwargs):

 context = super(YourView, self).get_context_data(**kwargs)
 context['YOUR_CUSTOM_SETTING'] = settings.YOUR_CUSTOM_SETTING

 return context

#
# in your_template.html, reference the setting like any other context variable
#
{{ YOUR_CUSTOM_SETTING }}
</code></pre>

blocks|key|1439481|text|我喜欢Berislav的解决方案，因为在简单的网站上，它干净而有效。我不喜欢的是随意暴露所有的设置常量。所以我最终做的是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1439482|from+django+import+template
from+django.conf+import+settings

register+=+template.Library()

ALLOWABLE_VALUES+=+("CONSTANT_NAME_1",+"CONSTANT_NAME_2",)

#+settings+value
@register.simple_tag
def+settings_value(name):
++++if+name+in+ALLOWABLE_VALUES:
++++++++return+getattr(settings,+name,+'')
++++return+''|code-block|syntax|javascript|1439483|用法：|1439484|{%25+settings_value+"CONSTANT_NAME_1"+%25}|1439485|这可以保护任何未命名的常量不会在模板中使用，如果你真的想在模板中使用，你可以在设置中设置一个元组，为不同的页面、应用程序或区域创建多个模板标签，并根据需要简单地将本地元组与设置元组组合，然后执行列表理解以查看该值是否可接受。|1439486|我同意，在一个复杂的站点上，这有点简单化了，但是在模板中有通用的值是很好的，而且这似乎工作得很好。感谢Berislav的原始想法！|1439487|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I like Berislav's solution, because on simple sites, it is clean and effective. What I do NOT like is exposing all the settings constants willy-nilly. So what I ended up doing was this:

<pre><code>from django import template
from django.conf import settings

register = template.Library()

ALLOWABLE_VALUES = ("CONSTANT_NAME_1", "CONSTANT_NAME_2",)

# settings value
@register.simple_tag
def settings_value(name):
 if name in ALLOWABLE_VALUES:
 return getattr(settings, name, '')
 return ''
</code></pre>

Usage:

<pre><code>{% settings_value "CONSTANT_NAME_1" %}
</code></pre>

This protects any constants that you have not named from use in the template, and if you wanted to get really fancy, you could set a tuple in the settings, and create more than one template tag for different pages, apps or areas, and simply combine a local tuple with the settings tuple as needed, then do the list comprehension to see if the value is acceptable. 
I agree, on a complex site, this is a bit simplistic, but there are values that would be nice to have universally in templates, and this seems to work nicely.
Thanks to Berislav for the original idea!

blocks|key|1654252|text|查看django-settings-export+(免责声明:我是此项目的作者)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1654253|例如..。|1654254|$+pip+install+django-settings-export|code-block|syntax|javascript|1654255|settings.py|1654256|TEMPLATES+=+[
++++{
++++++++'OPTIONS':+{
++++++++++++'context_processors':+[
++++++++++++++++'django_settings_export.settings_export',
++++++++++++],
++++++++},
++++},
]

MY_CHEESE+=+'Camembert';

SETTINGS_EXPORT+=+[
++++'MY_CHEESE',
]|1654257|template.html|1654258|<script>var+MY_CHEESE+=+'{{+settings.MY_CHEESE+}}';</script>|1654259|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/jakubroztocil/django-settings-export^0|2|M|2|M|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@$9|15|A|16|1|17]]|E|$]]|$1|F|3|G|5|6|7|18|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|19|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1A|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|1B|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1C|8|@]|D|@]|E|$]]|$1|S|3|T|5|J|7|1D|8|@]|D|@]|E|$K|L]]|$1|U|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]]]

Check out <a href="https://github.com/jakubroztocil/django-settings-export" rel="noreferrer"><code>django-settings-export</code></a> (disclaimer: I'm the author of this project).

For example...

<pre><code>$ pip install django-settings-export
</code></pre>

<h3>settings.py</h3>

<pre><code>TEMPLATES = [
 {
 'OPTIONS': {
 'context_processors': [
 'django_settings_export.settings_export',
 ],
 },
 },
]

MY_CHEESE = 'Camembert';

SETTINGS_EXPORT = [
 'MY_CHEESE',
]
</code></pre>

<h3>template.html</h3>

<pre><code>&lt;script&gt;var MY_CHEESE = '{{ settings.MY_CHEESE }}';&lt;/script&gt;
</code></pre>

blocks|key|1654303|text|如果有人像我一样发现这个问题，那么我会发布我的解决方案，它在Django+2.0上有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1654304|此标记将一些settings.py变量值分配给模板的变量：|1654305|用法：{%25+get_settings_value+template_var+"SETTINGS_VAR"+%25}|offset|length|style|CODE|1654306|app/templatetags/my_custom_tags.py：|1654307|from+django+import+template
from+django.conf+import+settings

register+=+template.Library()

class+AssignNode(template.Node):
++++def+__init__(self,+name,+value):
++++++++self.name+=+name
++++++++self.value+=+value

++++def+render(self,+context):
++++++++context[self.name]+=+getattr(settings,+self.value.resolve(context,+True),+"")
++++++++return+''

@register.tag('get_settings_value')
def+do_assign(parser,+token):
++++bits+=+token.split_contents()
++++if+len(bits)+!=+3:
++++++++raise+template.TemplateSyntaxError("'%25s'+tag+takes+two+arguments"+%25+bits[0])
++++value+=+parser.compile_filter(bits[2])
++++return+AssignNode(bits[1],+value)|code-block|syntax|javascript|1654308|您的模板：|1654309|{%25+load+my_custom_tags+%25}

#+Set+local+template+variable:
{%25+get_settings_value+settings_debug+"DEBUG"+%25}

#+Output+settings_debug+variable:
{{+settings_debug+}}

#+Use+variable+in+if+statement:
{%25+if+settings_debug+%25}
...+do+something+...
{%25+else+%25}
...+do+other+stuff+...
{%25+endif+%25}|1654310|请参阅Django的文档如何在此处创建自定义模板标记：https://docs.djangoproject.com/en/2.0/howto/custom-template-tags/|1654311|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.djangoproject.com/en/2.0/howto/custom-template-tags/^0|0|0|3|1G|0|0|0|0|0|R|1T|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|16|8|@$F|17|G|18|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|1A|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|T|5|N|7|1C|8|@]|9|@]|A|$O|P]]|$1|U|3|V|5|6|7|1D|8|@]|9|@$F|1E|G|1F|1|1G]]|A|$]]|$1|W|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

If someone finds this question like I did, then I'll post my solution which works on Django 2.0:

This tag assigns some settings.py variable value to template's variable:

Usage: <code>{% get_settings_value template_var "SETTINGS_VAR" %}</code>

<h2>app/templatetags/my_custom_tags.py:</h2>

<pre><code>from django import template
from django.conf import settings

register = template.Library()

class AssignNode(template.Node):
 def __init__(self, name, value):
 self.name = name
 self.value = value

 def render(self, context):
 context[self.name] = getattr(settings, self.value.resolve(context, True), "")
 return ''

@register.tag('get_settings_value')
def do_assign(parser, token):
 bits = token.split_contents()
 if len(bits) != 3:
 raise template.TemplateSyntaxError("'%s' tag takes two arguments" % bits[0])
 value = parser.compile_filter(bits[2])
 return AssignNode(bits[1], value)
</code></pre>

<h2>Your template:</h2>

<pre><code>{% load my_custom_tags %}

# Set local template variable:
{% get_settings_value settings_debug "DEBUG" %}

# Output settings_debug variable:
{{ settings_debug }}

# Use variable in if statement:
{% if settings_debug %}
... do something ...
{% else %}
... do other stuff ...
{% endif %}
</code></pre>

See Django's documentation how to create custom template tags here: <a href="https://docs.djangoproject.com/en/2.0/howto/custom-template-tags/" rel="nofollow noreferrer">https://docs.djangoproject.com/en/2.0/howto/custom-template-tags/</a>

blocks|key|1654348|text|对于那些想要使用@Berislav的方法(自定义模板标记)和if标记的人：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1654349|/app/templatetags/my_settings.py：|1654350|from+django+import+template
from+django.conf+import+settings

register+=+template.Library()

@register.simple_tag
def+settings_value(name):
++++return+getattr(settings,+name,+"")|code-block|syntax|javascript|1654351|模板文件：|1654352|
{%25+load+my_settings+%25}
{%25+settings_value+'ENABLE_FEATURE_A'+as+ENABLE_FEATURE_A+%25}

{%25+if+ENABLE_FEATURE_A+%25}

{%25+endif+%25}|1654353|entityMap^0|U|2|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|W|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|X|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|Q|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|R|$]]

For those who want to use @Berislav's approach (custom template tag) with <code>if</code> tag:
/app/templatetags/my_settings.py:
<pre><code>from django import template
from django.conf import settings

register = template.Library()

@register.simple_tag
def settings_value(name):
 return getattr(settings, name, &quot;&quot;)
</code></pre>
Template file:
<pre><code>&lt;!-- Load your tags --&gt;
{% load my_settings %}
{% settings_value 'ENABLE_FEATURE_A' as ENABLE_FEATURE_A %}

{% if ENABLE_FEATURE_A %}
&lt;!-- Feature A stuffs --&gt;
{% endif %}
</code></pre>

I have some stuff in settings.py that I'd like to be able to access from a template, but I can't figure out how to do it. I already tried

<pre><code>{{CONSTANT_NAME}}
</code></pre>

but that doesn't seem to work. Is this possible?

Can I access constants in settings.py from templates in Django?

Django

我在settings.py中有一些东西，我希望能够从模板访问，但我不知道如何做到这一点。我已经试过了{{CONSTANT_NAME}}但这似乎并不管用。这个是可能的吗？

问我可以从Django中的模板访问settings.py中的常量吗？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我可以从Django中的模板访问settings.py中的常量吗？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我可以从Django中的模板访问settings.py中的常量吗？
EN