On Sat, Jul 10, 2010 at 1:15 AM, Antoni Aloy <antoni.a...@gmail.com> wrote: > Hello, > > Have anybody (Marc Garcia ?) check > http://code.djangoproject.com/ticket/13621 ticket. It explains a bug > concerning date and time formats. The admin does not conform the i18n > locale settings on displaying time and date formats and reverts to the > default format. > > It seems a true regression test as > http://djangoadvent.com/1.2/i18n-l10n-improvements/ explains the right > display. I have reverted to Django 1.2.0 and the display works > perfectly. > > As you can imagine is a quite annoying bug for non-english date format > users, perhaps enough to make a 1.2.2 release.
Are you sure that this is a regression, rather than a bugfix with unfortunate side effects? In particular, I draw your attention to the second note under: http://docs.djangoproject.com/en/1.2/topics/i18n/localization/#id3 The reason for this change is that Python's date parsing libraries aren't thread safe, so parsing internationalized date/time components like AM/PM are problematic. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
