Re: TIMEZONE default

Thank you Alex and Aymeric for your responses. Since that is the situation, maybe an explanation should be included in the settings documentation? On Saturday, February 9, 2013 5:51:51 PM UTC-5, Aymeric Augustin wrote: > > Alex' answer is correct — and "later on" is actually a few days ago :) >

Re: TIMEZONE default

Alex' answer is correct — and "later on" is actually a few days ago :) UTC isn't a best practice as much as a country-agnostic practice. You're supposed to put your own time zone there. There are a few other discrepancies between global_settings.py and the default project template, notably

Re: TIMEZONE default

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

TIMEZONE default

Hey everybody, Quick question. In version 1.6 why is TIME_ZONE in django.conf.global_settings set to 'America/Chicago', but in the default project template TIME_ZONE = 'UTC'? Shouldn't they be the same, and if so