Opened 18 years ago

Closed 17 years ago

Last modified 16 years ago

#1120 closed defect (duplicate)

Development server ignores changing the TIME_ZONE information

Reported by: Marek Kubica Owned by: Adrian Holovaty
Component: runserver Version:
Severity: minor Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


While I was trying different time zones in (edit the file, save it, see the development server reloading) I noticed that the change of TIME_ZONE does not affect the server. You have to stop the server completely and restart it to let it see the change.

Change History (6)

comment:1 Changed 18 years ago by anonymous

Now, even after I restart the server completely, the TIME_ZONE still does not affect the server. Indeed, it seems that the TIME_ZONE setting has no effect at all.

comment:2 Changed 18 years ago by Adrian Holovaty

Resolution: worksforme
Status: newclosed

Please reopen with more information, such as your OS, database engine and Django version, if this is still an issue.

comment:3 Changed 18 years ago by scott.benjamin@…

Resolution: worksforme
Status: closedreopened

This happens to me on Windows XP, Python 2.4.3, with Django from trunk as of June 9 14:00 GMT using the SQLite db engine.

I am in New Zealand GMT +12 and no matter what timezone I set the TIME_ZONE setting to it only displays GMT in the output from the servers as well as the templates using {% now %}

comment:4 Changed 18 years ago by Malcolm Tredinnick

The other important question here is what is the value of your TIME_ZONE string in I'm wondering how much this is related to #1977.

comment:5 Changed 17 years ago by Adrian Holovaty

Component: runserver

comment:6 Changed 17 years ago by Chris Beaven

Resolution: duplicate
Status: reopenedclosed

Duplicate of #2315

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