Opened 13 years ago

Closed 13 years ago

Last modified 12 years ago

#179 closed defect (invalid)

Time zone doesn't work right under runserver

Reported by: edgars@… Owned by: Adrian Holovaty
Component: Core (Management commands) Version:
Severity: normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


No problems with mod_python though

Change History (4)

comment:1 Changed 13 years ago by Jacob

Resolution: worksforme
Status: newclosed

There's not enough information about what "doesn't work" (i.e. it works fine for me); please reopen with more data if you've got it.

comment:2 Changed 13 years ago by matt@…

Resolution: worksforme
Status: closedreopened

I'm having the same problem (haven't checked with mod_python though).

I'm in New Zealand. If I set (in .settings.main)

TIME_ZONE = "NZDT" # (New Zealand Daylight-Saving Time)


TIME_ZONE = "Pacific/Auckland NZ"

The time is incorrectly reported (both by the server's status line, and by any objects with an "auto_now" or "auto_now_add") as 12 hours behind what it really is. Setting TIME_ZONE to "GTM-12" works correctly, but will unfortunately no longer work correctly during New Zealand's summer, when we move to daylight-saving time.

All of the above settings are listed in the Postgres document referenced in conf/

comment:3 Changed 13 years ago by Adrian Holovaty


comment:4 Changed 13 years ago by Adrian Holovaty

Resolution: invalid
Status: reopenedclosed

Please reopen if you're still having the problem.

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