Changes between Initial Version and Version 1 of Ticket #17009


Ignore:
Timestamp:
Oct 7, 2011, 2:08:46 AM (13 years ago)
Author:
Aymeric Augustin
Comment:

​The docs link to a ​list of valid time zone choices. I think TIME_ZONE = "Etc/GMT-8" should do what you want.

The change you mention is a bugfix for #3415 introduced at r13722. It reveals the problem, but the root cause is still the fact that your TIME_ZONE setting is invalid. It isn't a bug in 1.3; the bug really was in 1.2 who should have warned you already.

Historically, Django hasn't sufficiently validated the value of settings.TIME_ZONE. It must be a timezone your system knows (ie. a file in /usr/share/zoneinfo) for time.tzset() to work properly. It must also be a timezone PostgreSQL knows if you're using the PostgreSQL backend.

I hope this helps. Thanks for the report!

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #17009

    • Property Resolution → invalid
    • Property Status new → closed

  • Ticket #17009 – Description

    initial v1  
    1 I use Ubuntu 8.04. I have found the source code in /usr/lib/python2.5/site-packages/django/conf/__init__.py has changed since version 1.2.3 and caused this problem. The following code is added by version 1.3.0:
     1I use Ubuntu 8.04. I have found the source code in `/usr/lib/python2.5/site-packages/django/conf/__init__.py` has changed since version 1.2.3 and caused this problem. The following code is added by version 1.3.0:
    22
     3{{{
    34 zoneinfo_root = '/usr/share/zoneinfo'
    45            if (os.path.exists(zoneinfo_root) and not
    … …  
    67                raise ValueError("Incorrect timezone setting: %s" % self.TIME_ZONE)
    78
     9}}}
Back to Top