2011/11/18 Anssi Kääriäinen <anssi.kaariai...@thl.fi> > 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. >
Ah, yes, that's an good point. It's very easy to intercept naive datetimes that reach the database adapter: https://code.djangoproject.com/browser/django/trunk/django/db/models/fields/__init__.py#L788 I considered adding a warning there, but I decided against it because I thought it would be too obnoxious. This deserves further thought. -- 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.
