diff options
| author | Tim Graham <timograham@gmail.com> | 2016-08-19 14:47:06 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-08-19 14:47:06 -0400 |
| commit | d60386d0f5333c7fef4c5906a3358b00cf9de3bf (patch) | |
| tree | 83641335917b9dec21c5fd359e7ea566a0e38551 | |
| parent | 4f138fe5a496a81115c4fba6615a517fc62c3b17 (diff) | |
Fixed #26571 -- Corrected recommendation for converting timestamps to tz-aware datetimes.
| -rw-r--r-- | docs/topics/i18n/timezones.txt | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/docs/topics/i18n/timezones.txt b/docs/topics/i18n/timezones.txt index e9abc22f59..8392d0c09f 100644 --- a/docs/topics/i18n/timezones.txt +++ b/docs/topics/i18n/timezones.txt @@ -151,10 +151,8 @@ used. backwards-compatibility with applications that still rely on local time. However, :ref:`as explained above <naive-datetime-objects>`, this isn't entirely reliable, and you should always work with aware datetimes in UTC - in your own code. For instance, use - :meth:`~datetime.datetime.utcfromtimestamp` instead of - :meth:`~datetime.datetime.fromtimestamp` -- and don't forget to set - ``tzinfo`` to :data:`~django.utils.timezone.utc`. + in your own code. For instance, use :meth:`~datetime.datetime.fromtimestamp` + and set the ``tz`` parameter to :data:`~django.utils.timezone.utc`. Selecting the current time zone ------------------------------- |