Hi Jonathan, I don't know the particular history of this setting, but this sounds like something that was done to maintain backwards compatibility. My guess is that when Django was first released, it defaulted to 'America/Chicago' but later on it was recognized that using UTC time on the server is a better way of handling times. As a result, if the settings module doesn't contain a TIME_ZONE setting, then you get 'America/Chicago' in order to be backwards compatible, but when you make a new project you get the current best-practice setting which is UTC.
Best, Alex Ogier On Sat, Feb 9, 2013 at 12:21 PM, Jonathan Loy <[email protected]> wrote: > Hey everybody, > > Quick question. In version 1.6 why is TIME_ZONE in > django.conf.global_settings<https://github.com/django/django/blob/master/django/conf/global_settings.py> > set > to 'America/Chicago', but in the default project template TIME_ZONE = > 'UTC'? Shouldn't they be the same, and if so which one? Thanks for taking > the time to read/answer my queston. > > > v/r > Jonathan > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-developers?hl=en > . > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
