默认Settings

一个django Settings�以为空,如果你�需�的�。�一个Settings有一个切�实际的默认值，这些默认值值在文件 django/conf/global_settings.py 里。

下�是django在编译settings文件时�用的规则：

• 从 global_settings.py 装载settings .

• 从指定settings 文件装载settings , 在需è¦�的时候，覆盖全局的settings

注�一个settings 文件�应该导入 global_settings ，因为那是多余（冗余）的。

查看你已�改�了哪些Settings

有一个容易的方法�查看你的哪些Settings 和默认的Settings ��，命令行 manage.py diffsettings �以显示当�的settings 文件文件和默认的settings 的��之处。

manage.py 的更详细�述在附录G，

在Python代�中使Settings

在你的Django应用程�中,从对象 django.conf.settings 导入settings使用，例如:

from django.conf import settings

if settings.DEBUG:
    # Do something

注� django.conf.settings �是一个模�，而是一个对象。所以�能�独导入settings：

from django.conf.settings import DEBUG  # This won't work.

�样�注�，你的代�中 � 应该导入 global_settings 或者自己的settings文件。 django.conf.settings 抽象了默认的设置和�个站点的设置；它�供了一个�一的接�。并且，它也使得你所写的代�与你的设置文件的�置没有耦�。

�行期间修改Settings

你�应该在你的应用程��行期间修改设置, 例如, ��在view里��这样的事情:

from django.conf import settings

settings.DEBUG = True   # Don't do this!

settings文件应该是唯一个修改 settings 的地方.

安全

因为settings文件包��感信�,例如数�库密�,你应该�试�制访问它.例如,改�它的文件��使得�有你和你的Web�务器用户���能读�它.这在共享主机环境中尤其��.

创建你自已的Settings

没有什么能够阻止你为自己创建的Django应用创建settings。 ���守以下约定：

• 为所有的é…�ç½®å��使用大写字æ¯�。

• 对于集å�ˆåž‹çš„设置，使用元组（tuple），而ä¸�è¦�使用列表（list）。所有的设置应该是互斥的，并且一旦确定以å�Žå°±ä¸�应该å†�改å�˜ã€‚使用元组也å��映了这样的ç�†å¿µã€‚

• ä¸�è¦�é‡�新创建已ç»�存在的setting。

django-admin.py 工具

当使用 django-admin.py （�附录G）时，你�以一次性设置环境��或者在�次�行这个工具时于settings模�中明确指明。

这是一个使用Unix Bash Shell的例�：

export DJANGO_SETTINGS_MODULE=mysite.settings
django-admin.py runserver

这是一个使用Windows命令行的例�：

set DJANGO_SETTINGS_MODULE=mysite.settings
django-admin.py runserver

使用 --settings 命令行�数�手工指明settings：

django-admin.py runserver --settings=mysite.settings

由 startproject 创建的作为工程骨架一部分的 manage.py 工具会自动设置 DJANGO_SETTINGS_MODULE` ；关于 manage.py 的详细说明�附录G。

�务器端(mod_python)

在你的实际�务器环境中，你需�告诉Apache/mod_python使用哪一个settings文件。通过 SetEnv ：

<Location "/mysite/">
    SetHandler python-program
    PythonHandler django.core.handlers.modpython
    SetEnv DJANGO_SETTINGS_MODULE mysite.settings
</Location>

�了解更详细的信�，请阅读Django mod_python在线手册 http://www.djangoproject.com/documentation/0.96/modpython/ 。

定制默认的Settings

如果你想从 django.conf.global_settings 以外的地方获得默认设置，你�以传入一个�供默认设置当作 default_settings 的�数（或者当作第一个�数) 到回调函数 configure()。

在下�的列�中，默认设置是是从myapp_defaults获�的，且DEBUG是设置为True, regardless of its value in myapp_defaults :

from django.conf import settings
from myapp import myapp_defaults

settings.configure(default_settings=myapp_defaults, DEBUG=True)

下�的例�是等价的：

settings.configure(myapp_defaults, DEBUG = True)

一般而言,您無需改變其�設值. 您應該�以安全平順地使用 Django 的�設值. �注�的是,一旦傳進一組新的�設模組,所有的 Django �設資料將會全部被*�代*,因此,必須在輸入程�碼時,���一個�能的設定給值. 請查閱 django.conf.settings.global_settings 了解所有的相關設定.

configure()或DJANGO_SETTINGS_MODULE之一是必须的

如果你没有设置``DJANGO_SETTINGS_MODULE``环境��，你必须在使用任何读�设置的代�之�的�处调用``configure()`` 方法。

如果你没有设置``DJANGO_SETTINGS_MODULE`` 也没有调用``configure()``，当第一次�个setting被访问时，Django 将会出现``EnvironmentError`` 异常。

If you set DJANGO_SETTINGS_MODULE , access settings values somehow, and then call configure() , Django will raise an EnvironmentError stating that settings have already been configured.

�外，�止一次或在任何setting已�被访问之�调用``configure()`` 都是错误的。

It boils down to this: use exactly one of either configure() or DJANGO_SETTINGS_MODULE . Not both, and not neither.

ABSOLUTE_URL_OVERRIDES

默认 : {} (empty dictionary)

000000000000000000000000000000

ABSOLUTE_URL_OVERRIDES = {
    'blogs.weblog': lambda o: "/blogs/%s/" % o.slug,
    'news.story': lambda o: "/stories/%s/%s/" % (o.pub_year, o.slug),
}

Note that the model name used in this setting should be all lowercase, regardless of the case of the actual model class name.

ADMIN_FOR

默认 : () (empty list)

This setting is used for admin site settings modules. It should be a tuple of settings modules (in the format 'foo.bar.baz' ) for which this site is an admin.

The admin site uses this in its automatically introspected documentation of models, views, and template tags.

ADMIN_MEDIA_PREFIX

默认 : '/media/'

此设置是用�设置管�模�的��文件（包括CSS，JavaScript和图�）URL的�缀。注��使用斜线

ADMINS

默认 : () (empty tuple)

This is a tuple that lists people who get code error notifications. When DEBUG=False and a view raises an exception, Django will email these people with the full exception information. Each member of the tuple should be a tuple of (Full name, e-mail address), for example:

(('John', 'john@example.com'), ('Mary', 'mary@example.com'))

�当一个错误被�获的时候，Django 将��给所有这些人

ALLOWED_INCLUDE_ROOTS

默认 : () (empty tuple)

This is a tuple of strings representing allowed prefixes for the {% ssi %} template tag. This is a security measure, so that template authors cant access files that they shouldnt be accessing.

For example, if ALLOWED_INCLUDE_ROOTS is ('/home/html', '/var/www') , then {% ssi /home/html/foo.txt %} would work, but {% ssi /etc/passwd %} wouldnt.

APPEND_SLASH

默认 : True

当此设置项为True的时候，系统会自动在URL的尾部加上一个å��æ–œæ� ’/’。这个设置项仅仅在安装了``CommonMiddleware``的状æ€�下使用（详è§�第15章）的``PREPEND_WWW``

CACHE_BACKEND

默认 : 'simple://'

指定使用的缓存�端（�第 13 章）。

CACHE_MIDDLEWARE_KEY_PREFIX

默认 : '' (empty string)

This is the cache key prefix that the cache middleware should use (see Chapter 13).

DATABASE_ENGINE

默认 : '' (empty string)

该设置用于指定使用下列哪�数�库作为存储�端: 'postgresql_psycopg2' , 'postgresql' , 'mysql' , 'mysql_old' or 'sqlite3' .

DATABASE_HOST

默认 : '' (empty string)

该设置指定连接数�库时所使用的主机。空字符串表示``localhost`` 。如果你使用SQLite，则�用设置该值。

如果你在使用MySQL，而这个值是以�斜线('/' )开头，那么MySQL将通过指定的Unix socket进行连接：

DATABASE_HOST = '/var/run/mysql'

如果你在使用MySQL，而这个值�没有以�斜线开头，那么这个值就被视为是主机。

DATABASE_NAME

默认 : '' (empty string)

该设置为所使用数�库的�称。如果使用SQLite，该设置为数�库文件的完整路径。

DATABASE_OPTIONS

默认 : {} (empty dictionary)

This is extra parameters to use when connecting to the database. Consult the back-end modules document for available keywords.

DATABASE_PASSWORD

默认 : '' (empty string)

该设置为数�库连接密�。如果使用SQLite，则�用设置。

DATABASE_PORT

默认 : '' (empty string)

这是用�连接数�库的端�. 空字符代表缺�端�. SQLite �用设置.

DATABASE_USER

默认 : '' (empty string)

该设置为连接数�库的用户�。当使用 SQLite 时无效。

DATE_FORMAT

默认 : 'N j, Y' (e.g., Feb. 4, 2003 )

This is the default formatting to use for date fields on Django admin change-list pages and, possibly, by other parts of the system. It accepts the same format as the now tag (see Appendix F, Table F-2).

�� DATETIME_FORMAT , TIME_FORMAT , YEAR_MONTH_FORMAT , 和 MONTH_DAY_FORMAT .

DATETIME_FORMAT

默认 : 'N j, Y, P' (例如, Feb. 4, 2003, 4 p.m. )

This is the default formatting to use for datetime fields on Django admin change-list pages and, possibly, by other parts of the system. It accepts the same format as the now tag (see Appendix F, Table F-2).

�� DATE_FORMAT , DATETIME_FORMAT , TIME_FORMAT , YEAR_MONTH_FORMAT , 和 MONTH_DAY_FORMAT .

DEBUG

默认 : False

这个设置项是一个标示debug开关的布尔值。

If you define custom settings, django/views/debug.py has a HIDDEN_SETTINGS regular expression that will hide from the DEBUG view anything that contains 'SECRET , PASSWORD , or PROFANITIES' . This allows untrusted users to be able to give backtraces without seeing sensitive (or offensive) settings.

Still, note that there are always going to be sections of your debug output that are inappropriate for public consumption. File paths, configuration options, and the like all give attackers extra information about your server. Never deploy a site with DEBUG turned on.

DEFAULT_CHARSET

默认 : 'utf-8'

This is the default charset to use for all HttpResponse objects, if a MIME type isnt manually specified. It is used with DEFAULT_CONTENT_TYPE to construct the Content-Type header. See Appendix H for more about HttpResponse objects.

DEFAULT_CONTENT_TYPE

默认 : 'text/html'

This is the default content type to use for all HttpResponse objects, if a MIME type isnt manually specified. It is used with DEFAULT_CHARSET to construct the Content-Type header. See Appendix H for more about HttpResponse objects.

DEFAULT_FROM_EMAIL

默认 : 'webmaster@localhost'

This is the default email address to use for various automated correspondence from the site manager(s).

DISALLOWED_USER_AGENTS

默认 : () (empty tuple)

This is a list of compiled regular expression objects representing User-Agent strings that are not allowed to visit any page, systemwide. Use this for bad robots/crawlers. This is used only if CommonMiddleware is installed (see Chapter 15).

EMAIL_HOST

默认 : 'localhost'

This is the host to use for sending email. See also EMAIL_PORT .

EMAIL_HOST_PASSWORD

默认 : '' (empty string)

This is the password to use for the SMTP server defined in EMAIL_HOST . This setting is used in conjunction with EMAIL_HOST_USER when authenticating to the SMTP server. If either of these settings is empty, Django wont attempt authentication.

�� EMAIL_HOST_USER .

EMAIL_HOST_USER

默认 : '' (empty string)

This is the username to use for the SMTP server defined in EMAIL_HOST . If its empty, Django wont attempt authentication. See also EMAIL_HOST_PASSWORD .

EMAIL_PORT

默认 : 25

This is the port to use for the SMTP server defined in EMAIL_HOST .

EMAIL_SUBJECT_PREFIX

默认 : '[Django] '

This is the subject-line prefix for email messages sent with django.core.mail.mail_admins or django.core.mail.mail_managers . Youll probably want to include the trailing space.

FIXTURE_DIRS

默认 : () (empty tuple)

This is a list of locations of the fixture data files, in search order. Note that these paths should use Unix-style forward slashes, even on Windows. It is used by Djangos testing framework, which is covered online at http://www.djangoproject.com/documentation/0.96/testing/.

IGNORABLE_404_ENDS

默认 : ('mail.pl', 'mailform.pl', 'mail.cgi', 'mailform.cgi', 'favicon.ico', '.php')

�� IGNORABLE_404_STARTS 和 Error reporting via e-mail .

IGNORABLE_404_STARTS

默认 : ('/cgi-bin/', '/_vti_bin', '/_vti_inf')

This is a tuple of strings that specify beginnings of URLs that should be ignored by the 404 emailer. See also SEND_BROKEN_LINK_EMAILS and IGNORABLE_404_ENDS .

INSTALLED_APPS

默认 : () (empty tuple)

A tuple of strings designating all applications that are enabled in this Django installation. Each string should be a full Python path to a Python package that contains a Django application. See Chapter 5 for more about applications.

INTERNAL_IPS

默认 : () (empty tuple)

A tuple of IP addresses, as strings, that

• See debug comments, when DEBUG is True

• Receive X headers if the XViewMiddleware is installed (see Chapter 15)

JING_PATH

默认 : '/usr/bin/jing'

This is the path to the Jing executable. Jing is a RELAX NG validator, and Django uses it to validate each XMLField in your models. See http://www.thaiopensource.com/relaxng/jing.html.

LANGUAGE_CODE

默认 : 'en-us'

This is a string representing the language code for this installation. This should be in standard language format for example, U.S. English is "en-us" . See Chapter 18.

LANGUAGES

Default : A tuple of all available languages. This list is continually growing and any copy included here would inevitably become rapidly out of date. You can see the current list of translated languages by looking in django/conf/global_settings.py .

The list is a tuple of two-tuples in the format (language code, language name) for example, ('ja', 'Japanese') . This specifies which languages are available for language selection. See Chapter 18 for more on language selection.

Generally, the default value should suffice. Only set this setting if you want to restrict language selection to a subset of the Django-provided languages.

If you define a custom LANGUAGES setting, its OK to mark the languages as translation strings, but you should never import django.utils.translation from within your settings file, because that module in itself depends on the settings, and that would cause a circular import.

The solution is to use a dummy gettext() function. Heres a sample settings file:

gettext = lambda s: s

LANGUAGES = (
    ('de', gettext('German')),
    ('en', gettext('English')),
)

With this arrangement, make-messages.py will still find and mark these strings for translation, but the translation wont happen at runtime so youll have to remember to wrap the languages in the real gettext() in any code that uses LANGUAGES at runtime.

MANAGERS

默认 : () (empty tuple)

This tuple is in the same format as ADMINS that specifies who should get broken-link notifications when SEND_BROKEN_LINK_EMAILS=True .

MEDIA_ROOT

默认 : '' (empty string)

This is an absolute path to the directory that holds media for this installation (e.g., "/home/media/media.lawrence.com/" ). See also MEDIA_URL .

MEDIA_URL

默认 : '' (empty string)

This URL handles the media served from MEDIA_ROOT (e.g., "http://media.lawrence.com" ).

Note that this should have a trailing slash if it has a path component:

• 正确 : "http://www.example.com/static/"

• 错误 : "http://www.example.com/static"

MIDDLEWARE_CLASSES

默认 :

("django.contrib.sessions.middleware.SessionMiddleware",
 "django.contrib.auth.middleware.AuthenticationMiddleware",
 "django.middleware.common.CommonMiddleware",
 "django.middleware.doc.XViewMiddleware")

This is a tuple of middleware classes to use. See Chapter 15.

MONTH_DAY_FORMAT

默认 : 'F j'

This is the default formatting to use for date fields on Django admin change-list pages and, possibly, by other parts of the system in cases when only the month and day are displayed. It accepts the same format as the now tag (see Appendix F, Table F-2).

For example, when a Django admin change-list page is being filtered by a date, the header for a given day displays the day and month. Different locales have different formats. For example, U.S. English would have January 1, whereas Spanish might have 1 Enero.

�� DATE_FORMAT , DATETIME_FORMAT , TIME_FORMAT , 和 YEAR_MONTH_FORMAT .

PREPEND_WWW

默认 : False

This setting indicates whether to prepend the www. subdomain to URLs that dont have it. This is used only if CommonMiddleware is installed (see the Chapter 15). See also APPEND_SLASH .

PROFANITIES_LIST

This is a tuple of profanities, as strings, that will trigger a validation error when the hasNoProfanities validator is called.

We dont list the default values here, because that might bring the MPAA ratings board down on our heads. To view the default values, see the file django/conf/global_settings.py .

ROOT_URLCONF

默认 : Not defined

This is a string representing the full Python import path to your root URLconf (e.g., "mydjangoapps.urls" ). See Chapter 3.

SECRET_KEY

默认 : (当你创建一个项目时自动生�)

This is a secret key for this particular Django installation. It is used to provide a seed in secret-key hashing algorithms. Set this to a random string the longer, the better. django-admin.py startproject creates one automatically and most of the time you wont need to change it

SEND_BROKEN_LINK_EMAILS

默认 : False

This setting indicates whether to send an email to the MANAGERS each time somebody visits a Django-powered page that is 404-ed with a nonempty referer (i.e., a broken link). This is only used if CommonMiddleware is installed (see Chapter 15). See also IGNORABLE_404_STARTS and IGNORABLE_404_ENDS .

SERIALIZATION_MODULES

默认 : Not defined.

Serialization is a feature still under heavy development. Refer to the online documentation at http://www.djangoproject.com/documentation/0.96/serialization/ for more information.

SERVER_EMAIL

默认 : 'root@localhost'

This is the email address that error messages come from, such as those sent to ADMINS and MANAGERS .

SESSION_COOKIE_AGE

默认 : 1209600 (两周，以秒计)

This is the age of session cookies, in seconds. See Chapter 12.

SESSION_COOKIE_DOMAIN

默认 : None

This is the domain to use for session cookies. Set this to a string such as ".lawrence.com" for cross-domain cookies, or use None for a standard domain cookie. See Chapter 12.

SESSION_COOKIE_NAME

默认 : 'sessionid'

This is the name of the cookie to use for sessions; it can be whatever you want. See Chapter 12.

SESSION_COOKIE_SECURE

默认 : False

This setting indicates whether to use a secure cookie for the session cookie. If this is set to True , the cookie will be marked as secure, which means browsers may ensure that the cookie is only sent under an HTTPS connection. See Chapter 12.

SESSION_EXPIRE_AT_BROWSER_CLOSE

默认 : False

This setting indicates whether to expire the session when the user closes his browser. See Chapter 12.

SESSION_SAVE_EVERY_REQUEST

默认 : False

This setting indicates whether to save the session data on every request. See Chapter 12.

SITE_ID

默认 : Not defined

这就是在“django_site�数�库表中当�网站的整数ID。它常用于应用程�数�能够挂钩到指定的网站，或�个数�库上能管�多个网站的内容。��第14章。

TEMPLATE_CONTEXT_PROCESSORS

默认 :

("django.core.context_processors.auth",
"django.core.context_processors.debug",
"django.core.context_processors.i18n")

This is 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 of items to be merged into the context. See Chapter 10.

TEMPLATE_DEBUG

默认 : False

This Boolean turns template debug mode on and off. If it is True , the fancy error page will display a detailed report for any TemplateSyntaxError . This report contains the relevant snippet of the template, with the appropriate line highlighted.

Note that Django only displays fancy error pages if DEBUG is True , so youll want to set that to take advantage of this setting.

�� DEBUG .

TEMPLATE_DIRS

默认 : () (empty tuple)

这是一个根��索排�的模��文件的�置列表。注�，这些路径应该使用Unix风格的分割符，�使在Windows上。�加第4和10章。

TEMPLATE_LOADERS

默认 : ('django.template.loaders.filesystem.load_template_source',)

This is a tuple of callables (as strings) that know how to import templates from various sources. See Chapter 10.

TEMPLATE_STRING_IF_INVALID

默认 : '' (Empty string)

This is output, as a string, that the template system should use for invalid (e.g., misspelled) variables. See Chapter 10.

TEST_RUNNER

默认 : 'django.test.simple.run_tests'

这是用于�动测试套件的方法�称。它用在Django测试框架中，��http://www.djangoproject.com/documentation/0.96/testing 。

TEST_DATABASE_NAME

默认 : None

这是用于执行测试套件的数æ�®å��称。如果该值为None, 那么测试数æ�®åº“将会使用å��称’test_‘ + settings.DATABASE_NAME。å�‚è§�Django测试框架的文档，ä½�于http://www.djangoproject.com/documentation/0.96/testing/ 。

TIME_FORMAT

默认 : 'P' (e.g., 4 p.m. )

This is the default formatting to use for time fields on Django admin change-list pages and, possibly, by other parts of the system. It accepts the same format as the now tag (see Appendix F, Table F-2).

�� DATE_FORMAT , DATETIME_FORMAT , TIME_FORMAT , YEAR_MONTH_FORMAT , 和 MONTH_DAY_FORMAT .

TIME_ZONE

默认 : 'America/Chicago'

此字符串表示安装的时区。时区为Unix标准的zic格�。在http://www.postgresql.org/docs/8.1/static/dateime-keywords.html#DATETIME-TIMEZONE-SET-TABLE上有一个相对完整的时区字符串列表。

这是Django转�包括�务器时区在内的所有日期�时间时所用的时区。例如，一个�务器�以托管多个Django站点，�个站点有一个独立的时区设置。

Normally, Django sets the os.environ['TZ'] variable to the time zone you specify in the TIME_ZONE setting. Thus, all your views and models will automatically operate in the correct time zone. However, if youre using the manually configuring settings (described above in the section titled Using Settings Without Setting DJANGO_SETTINGS_MODULE), Django will not touch the TZ environment variable, and it will be up to you to ensure your processes are running in the correct environment.

注�

Django�能��地使用Windows环境里的�选时区。如果你在Windows上�行Django，这个��必须设置为与系统时区一致。

URL_VALIDATOR_USER_AGENT

默认 : Django/<version> (http://www.djangoproject.com/)

这是当检查url是�存在时用于“User-Agent�的字符串（ ��“URLField�的“verify_exists�选项；��附录B）。

USE_ETAGS

默认 : False

此逻辑值指定是�输出ETag�缀。这会节�带宽但是�低性能。一般�有当安装了时�使用此选项（��第15章）。

USE_I18N

默认 : True

此逻辑值指定Django国际化系统（��第18章）是��用。这�供了一个因为性能而关闭国际化的简�方法。如果此值设为“False�,Django将会�一些优化以替代未加载的国际化机制。

YEAR_MONTH_FORMAT

默认 : 'F Y'

这是默认格�，用于Django管��更列表页�的日期域，并且有�能，也用于系统其他部分的�显示年月的情况。“now�标签接�相�的格�。（��附录F）。

例如，当一个Django管��更列表也被一个日期过滤时，给出的月份�缀会显示出年月。��的地区有��的格�，比如美国英语会使用January 2006，而其他地区�能使用2006/January。

�� DATE_FORMAT , DATETIME_FORMAT , TIME_FORMAT , 和 MONTH_DAY_FORMAT .