On 18 November 2011 16:57, Anssi Kääriäinen <anssi.kaariai...@thl.fi> wrote: > My point is that it would be very useful to know you are actually > using aware datetimes internally. Especially when migrating an old > project to use this feature, it is easy to miss some places that do > not use aware datetimes. And you might find it out when you hit an > hour where suddenly your webapp is failing all over the place. So the > setting I proposed would report usage of naive datetimes all the year, > so that you could spot the problems in testing, not in production.
Tying it to the DEBUG-option should be enough. If DEBUG is on, snitch on naive date times. If locale is on you can give a warning when in the danger zone, just before or after the DST-changeover. HM -- 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.
