#1977: Misleading timezone advice in settings.py
-------------------------------+--------------------------------------------
Reporter: Joeboy | Owner: adrian
Type: defect | Status: new
Priority: normal | Milestone:
Component: django-admin.py | Version: SVN
Severity: normal | Resolution:
Keywords: timezone datetime |
-------------------------------+--------------------------------------------
Comment (by mtredinnick):
To explain a bit more what the problem here is: if you set the timezone to
'Europe/London' then all the date/time functions respect DST settings.
With a string like 'Europe/London GB GB-Eire', it is internally mapped to
something like "UTC + 0 always" at some level (not sure whether it's in
the Python library or the C library). So, today, the longer setting for
TIME_ZONE will mean that datetime.datetime.now() inside Django will be
wrong (due to daylight savings being in effect in London).
PostgreSQL is too flexible in what it accepts. C libraries, not so much.
--
Ticket URL: <http://code.djangoproject.com/ticket/1977>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
