Default timezone settings are different from the operating systems'
|Reported by:||berdario||Owned by:||Aymeric Augustin|
|Cc:||Triage Stage:||Ready for checkin|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
The settings.py template reads:
"On Unix systems, a value of None will cause Django to use the same timezone as the operating system."
but by leaving the TIME_ZONE off, it will use the TIME_ZONE defined in the global_settings... compared to explicitly overriding it with None: that instead will indeed use a django.utils.timezone.LocalTimezone instance
this is quite unexpected
moreover: the django.utils.timezone code warns that in case of problems, you'd be better off with pytz than by trying to use LocalTimezone
so, using None to automatically detect the system timezone as suggested, will prevent django from using pytz, even if it was installed
I don't know if it's fine to suggest that None could be used without warning about that, but in case I think it would be better to
- change the value in django/conf/global_settings.py to None
- change the comments inside django/conf/project_template/project_name/settings.py