Opened 2 months ago

Closed 8 weeks ago

#35430 closed Cleanup/optimization (fixed)

Documentation about timezone is misleading

Reported by: younes-chaoui Owned by: い。
Component: Documentation Version: 5.0
Severity: Normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no


Official documentation says :

When support for time zones is enabled, Django stores datetime information in UTC in the database, uses time-zone-aware datetime objects internally, and translates them to the end user’s time zone in templates and forms.

This is not True. In templates (including admin panel), Django uses TIME_ZONE setting instead of end user's timezone.

Change History (8)

comment:1 by Sarah Boyce, 2 months ago

Component: UncategorizedDocumentation
Easy pickings: set
Triage Stage: UnreviewedAccepted
Type: UncategorizedCleanup/optimization

Yes thank you!
This is clearer further down in the "Time zone aware input in forms" and "Time zone aware output in templates" section.
I recommend that end user's time zone is updated to :ref:`default current time zone <default-current-time-zone>` here.

comment:2 by い。, 2 months ago

Owner: changed from nobody to い。
Status: newassigned

comment:3 by い。, 2 months ago

Has patch: set
Version 0, edited 2 months ago by い。 (next)

comment:4 by い。, 2 months ago

Last edited 2 months ago by い。 (previous) (diff)

comment:5 by Sarah Boyce, 2 months ago

Patch needs improvement: set

comment:6 by Sarah Boyce, 2 months ago

Patch needs improvement: unset

comment:7 by Sarah Boyce, 8 weeks ago

Triage Stage: AcceptedReady for checkin

comment:8 by Sarah Boyce <42296566+sarahboyce@…>, 8 weeks ago

Resolution: fixed
Status: assignedclosed

In 718ed69:

Fixed #35430 -- Corrected docs on timezone conversion in templates.

Note: See TracTickets for help on using tickets.
Back to Top