Code

Opened 7 years ago

Closed 7 years ago

Last modified 7 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
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.

Attachments (0)

Change History (6)

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

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

$ 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 7 years ago by SmileyChris

  • Resolution set to invalid
  • Status changed from new to closed

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 7 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 7 years ago by SmileyChris

  • Component changed from Core framework to Documentation
  • Resolution invalid deleted
  • Status changed from closed to reopened
  • Summary changed from settings.TIME_ZONE bug for 'America/Sao_Paulo Brazil/East' to Docs should mention that time zones on the pgSQL timezone table are space separated
  • Triage Stage changed from Unreviewed to Design 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 follow-up: Changed 7 years ago by mtredinnick

  • Resolution set to invalid
  • Status changed from reopened to closed

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 7 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!

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.