(subject changed because I'm forking the discussion) On 20 févr. 2012, at 21:29, Anssi Kääriäinen wrote:
> Another question I have meant to ask is if 1.4 is too early to have > USE_TZ = True as default setting? I am afraid there are still some > bugs to iron out, some documentation to improve, helper functions to > add and most of all the timezone handling might confuse new users. I was thinking about that too. The main reason for enabling time zone support by default in new projects (through the settings.py template) was to store UTC in the database (on SQLite, MySQL and Oracle; PostgreSQL always does that anyway). This decision was certainly skewed by my background in enterprise software, where reliable handling of datetimes is a no brainer. But this isn't the most common use case for Django. Python doesn't make it very easy to deal with time zones, so forcing that concept on developers isn't friendly. The "right way" to do things is impractical, and there isn't that much space for improvement. Besides, the average website doesn't need time zone support, and IRC discussions show that developers don't care. What do others think? -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
