Django基于Pycharm开发之三[LANGUAGE_CODE与TIME_ZONE]
2018-03-06 23:54
597 查看
在django/conf/global_settings.py 中,我们可以找到关于language和timezone的通用配置信息,源码如下:
在这里,我们可以找到关于language_code的缩写,对应的关于time_zone,我们可以在这里找到相关信息
Default:
A string representing the time zone for this installation. See the list of time zones.
Note
Since Django was first released with the
Note that this isn’t necessarily the time zone of the server. For example, one server may serve multiple Django-powered sites, each with a separate time zone setting.
When
On Unix environments (where
Note
Django cannot reliably use alternate time zones in a Windows environment. If you’re running Django on Windows,
看看官方这段的描述,所以当我们使用windows开发的时候,还是要注意以上的一些问题的。
# Local time zone for this installation. All choices can be found here: |
# https://en.wikipedia.org/wiki/List_of_tz_zones_by_name (although not all | |
# systems may support all possibilities). When USE_TZ is True, this is | |
# interpreted as the default user time zone. | |
TIME_ZONE = 'America/Chicago' | |
# If you set this to True, Django will use timezone-aware datetimes. | |
USE_TZ = False | |
# Language code for this installation. All choices can be found here: | |
# http://www.i18nguy.com/unicode/language-identifiers.html | |
LANGUAGE_CODE = 'en-us' | |
# Languages we provide translations for, out of the box. | |
LANGUAGES = [ | |
('af', gettext_noop('Afrikaans')), | |
('ar', gettext_noop('Arabic')), | |
('ast', gettext_noop('Asturian')), | |
('az', gettext_noop('Azerbaijani')), | |
('bg', gettext_noop('Bulgarian')), | |
('be', gettext_noop('Belarusian')), | |
('bn', gettext_noop('Bengali')), | |
('br', gettext_noop('Breton')), | |
('bs', gettext_noop('Bosnian')), | |
('ca', gettext_noop('Catalan')), | |
('cs', gettext_noop('Czech')), | |
('cy', gettext_noop('Welsh')), | |
('da', gettext_noop('Danish')), | |
('de', gettext_noop('German')), | |
('dsb', gettext_noop('Lower Sorbian')), | |
('el', gettext_noop('Greek')), | |
('en', gettext_noop('English')), | |
('en-au', gettext_noop('Australian English')), | |
('en-gb', gettext_noop('British English')), | |
('eo', gettext_noop('Esperanto')), | |
('es', gettext_noop('Spanish')), | |
('es-ar', gettext_noop('Argentinian Spanish')), | |
('es-co', gettext_noop('Colombian Spanish')), | |
('es-mx', gettext_noop('Mexican Spanish')), | |
('es-ni', gettext_noop('Nicaraguan Spanish')), | |
('es-ve', gettext_noop('Venezuelan Spanish')), | |
('et', gettext_noop('Estonian')), | |
('eu', gettext_noop('Basque')), | |
('fa', gettext_noop('Persian')), | |
('fi', gettext_noop('Finnish')), | |
('fr', gettext_noop('French')), | |
('fy', gettext_noop('Frisian')), | |
('ga', gettext_noop('Irish')), | |
('gd', gettext_noop('Scottish Gaelic')), | |
('gl', gettext_noop('Galician')), | |
('he', gettext_noop('Hebrew')), | |
('hi', gettext_noop('Hindi')), | |
('hr', gettext_noop('Croatian')), | |
('hsb', gettext_noop('Upper Sorbian')), | |
('hu', gettext_noop('Hungarian')), | |
('ia', gettext_noop('Interlingua')), | |
('id', gettext_noop('Indonesian')), | |
('io', gettext_noop('Ido')), | |
('is', gettext_noop('Icelandic')), | |
('it', gettext_noop('Italian')), | |
('ja', gettext_noop('Japanese')), | |
('ka', gettext_noop('Georgian')), | |
('kab', gettext_noop('Kabyle')), | |
('kk', gettext_noop('Kazakh')), | |
('km', gettext_noop('Khmer')), | |
('kn', gettext_noop('Kannada')), | |
('ko', gettext_noop('Korean')), | |
('lb', gettext_noop('Luxembourgish')), | |
('lt', gettext_noop('Lithuanian')), | |
('lv', gettext_noop('Latvian')), | |
('mk', gettext_noop('Macedonian')), | |
('ml', gettext_noop('Malayalam')), | |
('mn', gettext_noop('Mongolian')), | |
('mr', gettext_noop('Marathi')), | |
('my', gettext_noop('Burmese')), | |
('nb', gettext_noop('Norwegian Bokmål')), | |
('ne', gettext_noop('Nepali')), | |
('nl', gettext_noop('Dutch')), | |
('nn', gettext_noop('Norwegian Nynorsk')), | |
('os', gettext_noop('Ossetic')), | |
('pa', gettext_noop('Punjabi')), | |
('pl', gettext_noop('Polish')), | |
('pt', gettext_noop('Portuguese')), | |
('pt-br', gettext_noop('Brazilian Portuguese')), | |
('ro', gettext_noop('Romanian')), | |
('ru', gettext_noop('Russian')), | |
('sk', gettext_noop('Slovak')), | |
('sl', gettext_noop('Slovenian')), | |
('sq', gettext_noop('Albanian')), | |
('sr', gettext_noop('Serbian')), | |
('sr-latn', gettext_noop('Serbian Latin')), | |
('sv', gettext_noop('Swedish')), | |
('sw', gettext_noop('Swahili')), | |
('ta', gettext_noop('Tamil')), | |
('te', gettext_noop('Telugu')), | |
('th', gettext_noop('Thai')), | |
('tr', gettext_noop('Turkish')), | |
('tt', gettext_noop('Tatar')), | |
('udm', gettext_noop('Udmurt')), | |
('uk', gettext_noop('Ukrainian')), | |
('ur', gettext_noop('Urdu')), | |
('vi', gettext_noop('Vietnamese')), | |
('zh-hans', gettext_noop('Simplified Chinese')), | |
('zh-hant', gettext_noop('Traditional Chinese')), | |
] |
#something you want can find by https://github.com/django/django/blob/master/django/conf/global_settings.py # Local time zone for this installation. All choices can be found here: # https://en.wikipedia.org/wiki/List_of_tz_zones_by_name (although not all # systems may support all possibilities). When USE_TZ is True, this is # interpreted as the default user time zone.
TIME_ZONE
Default: 'America/Chicago'
A string representing the time zone for this installation. See the list of time zones.
Note
Since Django was first released with the
TIME_ZONEset to
'America/Chicago', the global setting (used if nothing is defined in your project’s
settings.py) remains
'America/Chicago'for backwards compatibility. New project templates default to
'UTC'.
Note that this isn’t necessarily the time zone of the server. For example, one server may serve multiple Django-powered sites, each with a separate time zone setting.
When
USE_TZis
False, this is the time zone in which Django will store all datetimes. When
USE_TZis
True, this is the default time zone that Django will use to display datetimes in templates and to interpret datetimes entered in forms.
On Unix environments (where
time.tzset()is implemented), Django sets the
os.environ['TZ']variable to the time zone you specify in the
TIME_ZONEsetting. Thus, all your views and models will automatically operate in this time zone. However, Django won’t set the
TZenvironment variable if you’re using the manual configuration option as described in manually configuring settings. If Django doesn’t set the
TZenvironment variable, it’s up to you to ensure your processes are running in the correct environment.
Note
Django cannot reliably use alternate time zones in a Windows environment. If you’re running Django on Windows,
TIME_ZONEmust be set to match the system time zone.
看看官方这段的描述,所以当我们使用windows开发的时候,还是要注意以上的一些问题的。
相关文章推荐
- Django设置TIME_ZONE和LANGUAGE_CODE为中国区域
- Django设置TIME_ZONE和LANGUAGE_CODE为中国区域
- Django基于Pycharm开发之二 [使用django adminSite]
- Django基于Pycharm开发之一【创建django工程】
- Django基于Pycharm开发之四[关于静态文件的使用,配置以及源码分析](原创)
- Django基于Pycharm开发之三[命名空间 与过滤器]
- Django(博客系统):按照时间分层筛选“/blog/article/?create_time__year=2017”,出现问题:Database returned an invalid datetime value. Are time zone definitions for your database installed?
- 基于Django开发的SkyNet博客三——登录注册界面
- 玩聚网目前也是基于Python的Django框架开发
- 基于Django的独立运行脚本开发
- 基于python、Django做Web开发
- [置顶] Python + C/C++ 嵌入式编程(2):基于Code::Blocks进行环境配置和开发(入门版)
- PyCharm中使用virtualenv进行django开发
- 使用pycharm手动搭建python语言django开发环境(一)
- Django 开发初探 (PyCharm+Django)
- 基于.NET Core的Hypertext Application Language(HAL)开发库
- vmaig_blog 一个基于 Django1.8 跟 Bootstrap3 开发的 博客系统
- Pycharm+Django+Python+MySQL开发 后台管理数据库
- 玩聚网目前也是基于Python的Django框架开发
- 安装django-cms报错,ImproperlyConfigured: LANGUAGE_CODE "en-us" must have a matching entry in LANGUAG解决办法