#1120 closed defect (duplicate)
Development server ignores changing the TIME_ZONE information
| Reported by: | Marek Kubica | Owned by: | Adrian Holovaty |
|---|---|---|---|
| Component: | django-admin.py 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 |
Description
While I was trying different time zones in settings.py (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 by , 19 years ago
comment:2 by , 18 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Please reopen with more information, such as your OS, database engine and Django version, if this is still an issue.
comment:3 by , 18 years ago
| Resolution: | worksforme |
|---|---|
| Status: | closed → reopened |
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 by , 18 years ago
The other important question here is what is the value of your TIME_ZONE string in settings.py? I'm wondering how much this is related to #1977.
comment:5 by , 18 years ago
| Component: | django-admin.py → django-admin.py runserver |
|---|
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.