You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ref/settings.txt
+34-20Lines changed: 34 additions & 20 deletions
Original file line number
Diff line number
Diff line change
@@ -1145,28 +1145,42 @@ TIME_ZONE
1145
1145
1146
1146
Default: ``'America/Chicago'``
1147
1147
1148
-
A string representing the time zone for this installation. `See available choices`_.
1149
-
(Note that list of available choices lists more than one on the same line;
1150
-
you'll want to use just one of the choices for a given time zone. For instance,
1151
-
one line says ``'Europe/London GB GB-Eire'``, but you should use the first bit
1152
-
of that -- ``'Europe/London'`` -- as your ``TIME_ZONE`` setting.)
1153
-
1154
-
Note that this is the time zone to which Django will convert all dates/times --
1155
-
not necessarily the timezone of the server. For example, one server may serve
1156
-
multiple Django-powered sites, each with a separate time-zone setting.
1157
-
1158
-
Normally, Django sets the ``os.environ['TZ']`` variable to the time zone you
1159
-
specify in the ``TIME_ZONE`` setting. Thus, all your views and models will
1160
-
automatically operate in the correct time zone. However, if you're manually
1161
-
:ref:`manually configuring settings
1162
-
<settings-without-django-settings-module>`, Django will *not* touch the ``TZ``
1163
-
environment variable, and it'll be up to you to ensure your processes are
1164
-
running in the correct environment.
1148
+
.. versionchanged:: 1.2
1149
+
``None`` was added as an allowed value.
1150
+
1151
+
A string representing the time zone for this installation, or
1152
+
``None``. `See available choices`_. (Note that list of available
1153
+
choices lists more than one on the same line; you'll want to use just
1154
+
one of the choices for a given time zone. For instance, one line says
1155
+
``'Europe/London GB GB-Eire'``, but you should use the first bit of
1156
+
that -- ``'Europe/London'`` -- as your ``TIME_ZONE`` setting.)
1157
+
1158
+
Note that this is the time zone to which Django will convert all
1159
+
dates/times -- not necessarily the timezone of the server. For
1160
+
example, one server may serve multiple Django-powered sites, each with
1161
+
a separate time-zone setting.
1162
+
1163
+
Normally, Django sets the ``os.environ['TZ']`` variable to the time
1164
+
zone you specify in the ``TIME_ZONE`` setting. Thus, all your views
1165
+
and models will automatically operate in the correct time zone.
1166
+
However, Django won't set the ``TZ`` environment variable under the
1167
+
following conditions:
1168
+
1169
+
* If you're using the manual configuration option as described in
1170
+
:ref:`manually configuring settings
1171
+
<settings-without-django-settings-module>`, or
1172
+
1173
+
* If you specify ``TIME_ZONE = None``. This will cause Django to fall
1174
+
back to using the system timezone.
1175
+
1176
+
If Django doesn't set the ``TZ`` environment variable, it's up to you
1177
+
to ensure your processes are running in the correct environment.
1165
1178
1166
1179
.. note::
1167
-
Django cannot reliably use alternate time zones in a Windows environment.
1168
-
If you're running Django on Windows, this variable must be set to match the
1169
-
system timezone.
1180
+
Django cannot reliably use alternate time zones in a Windows
1181
+
environment. If you're running Django on Windows, this variable
1182
+
must be set to match the system timezone.
1183
+
1170
1184
1171
1185
.. _See available choices: http://www.postgresql.org/docs/8.1/static/datetime-keywords.html#DATETIME-TIMEZONE-SET-TABLE
0 commit comments