Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#4505 closed (invalid)

Docs should mention that time zones on the pgSQL timezone table are space separated

Reported by: Guilherme M. Gondim (semente) <semente@…> Owned by: Adrian Holovaty
Component: Documentation Version: master
Severity: Keywords:
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

datetime doesn't work with settings.TIME_ZONE = 'America/Sao_Paulo Brazil/East'.

The correct is only 'America/Sao_Paulo', then is not equal than in http://www.postgresql.org/docs/8.1/static/datetime-keywords.html#DATETIME-TIMEZONE-SET-TABLE as suggested.

I uses a GNU/Linux system.

Change History (6)

comment:1 Changed 10 years ago by Guilherme M. Gondim (semente) <semente@…>

$ TZ='America/Sao_Paulo Brazil/East' date
Thu Jun 7 22:13:09 America/Sao_Paulo Brazil/East 2007

$ TZ='America/Sao_Paulo' date
Thu Jun 7 19:13:17 BRT 2007

comment:2 Changed 10 years ago by Chris Beaven

Resolution: invalid
Status: newclosed

Although it may not be clear at first glance, duplicate time zones are space separated in that table.
America/Sao_Paulo or Brazil/East should work fine.

comment:3 Changed 10 years ago by Guilherme M. Gondim (semente) <semente@…>

Hmm, ok.

Most users uses 'America/Sao_Paulo Brazil/East' like in Table B-6. of PostgreSQL documentation. If the entry 'America/Sao_Paulo Brazil/East' was 'America/Sao_Paulo *OR* Brazil/East', would be less confused. Why not create a page in Django Documentation for this?

Thanks!

comment:4 Changed 10 years ago by Chris Beaven

Component: Core frameworkDocumentation
Resolution: invalid
Status: closedreopened
Summary: settings.TIME_ZONE bug for 'America/Sao_Paulo Brazil/East'Docs should mention that time zones on the pgSQL timezone table are space separated
Triage Stage: UnreviewedDesign decision needed

Perhaps a note that multiple entries in the same time zone are space separated in that table would suffice.

I do actually remember encountering this when I first started with Django too (with the Pacific/Auckland NZ zone) so I'll reopen this for another opinion.

comment:5 Changed 10 years ago by Malcolm Tredinnick

Resolution: invalid
Status: reopenedclosed

The PostgreSQL documentation, in the very last line before the table referenced, explains that there is more than one timezone per line and our settings documentation (for TIME_ZONE) also documents that. If people aren't going to read the existing documentation, creating new documentation won't help the situation.

comment:6 in reply to:  5 Changed 10 years ago by Guilherme M. Gondim (semente) <semente@…>

Replying to mtredinnick:

The PostgreSQL documentation, in the very last line before the table referenced, explains that there is more than one timezone per line and our settings documentation (for TIME_ZONE) also documents that. If people aren't going to read the existing documentation, creating new documentation won't help the situation.

That is true, but in settings.py we have:

# Local time zone for this installation. Choices can be found here:
# http://www.postgresql.org/docs/8.1/static/datetime-keywords.html#DATETIME-TIMEZONE-SET-TABLE
# although not all variations may be possible on all operating systems.
# If running in a Windows environment this must be set to the same as your
# system time zone.
TIME_ZONE = 'America/Chicago'

Why not toggle the link to http://www.djangoproject.com/documentation/settings/#time-zone and add choices in more legible format?

Thanks!

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