On 9 mars 2014, at 17:41, Jon Dufresne <[email protected]> wrote:
> I use "date_format" so the dates are always formatted correctly and > consistently. ... assuming your application is only ever used in one locale. We cannot make this assumption for all Django applications. YYYY-MM-DD is unambiguous and consistent. You could argue that DD/MM/YYYY is just as good, but Americans tend to interpret it backwards (they read 10/12/2014 as October 12th instead of December 10th). Furthermore, there are two reasons why I'm against making this change in Django: - it's a large backwards incompatibility; - it deviates from Python's behavior in a surprising and unexpected way. If you want that feature, I would suggest to subclass DateTimeField in your projects. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/66ABF044-6273-4E57-A73D-7FFEA3D9167B%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
