On Thu, 2006-07-06 at 11:20 +0800, Russell Keith-Magee wrote: > On 7/6/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: [...]
> One idea that was bounced around in my conversation with the > client was > that TIME_ZONE defaults to empty (or None, preferably) and if, > not set, > does not get inserted into the environment. Personally, I > don't really > care too much about this, since it's such a trivial thing to > set. > > This seems like a reasonable idea to me. It has always slightly bugged > me that the default timezone is America/Chicago, and I have to modify > it on every project. Yes, it is a trivial thing to set, but 'system > clock/no specific timezone' would be a better default than > 'Chicago' (for everyone except Adrian, that is :-). The argument in favour of this is gathering strength: I just tried to work out #2315 and, essentially, we're playing with fire trying to set TZ on Windows systems. At least giving those people the option of setting TIME_ZONE = None so that we don't mess up their existing settings would be nicer than our current slightly misguided attempts. Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers -~----------~----~----~----~------~----~------~--~---
