Fixed #26571 -- Corrected recommendation for converting timestamps to tz-aware datetimes.
This commit is contained in:
parent
4f138fe5a4
commit
d60386d0f5
|
@ -151,10 +151,8 @@ used.
|
||||||
backwards-compatibility with applications that still rely on local time.
|
backwards-compatibility with applications that still rely on local time.
|
||||||
However, :ref:`as explained above <naive-datetime-objects>`, this isn't
|
However, :ref:`as explained above <naive-datetime-objects>`, this isn't
|
||||||
entirely reliable, and you should always work with aware datetimes in UTC
|
entirely reliable, and you should always work with aware datetimes in UTC
|
||||||
in your own code. For instance, use
|
in your own code. For instance, use :meth:`~datetime.datetime.fromtimestamp`
|
||||||
:meth:`~datetime.datetime.utcfromtimestamp` instead of
|
and set the ``tz`` parameter to :data:`~django.utils.timezone.utc`.
|
||||||
:meth:`~datetime.datetime.fromtimestamp` -- and don't forget to set
|
|
||||||
``tzinfo`` to :data:`~django.utils.timezone.utc`.
|
|
||||||
|
|
||||||
Selecting the current time zone
|
Selecting the current time zone
|
||||||
-------------------------------
|
-------------------------------
|
||||||
|
|
Loading…
Reference in New Issue