On Tue, Jul 13, 2010 at 9:48 AM, Jannis Leidel <jan...@leidel.info> wrote: > > Am 13.07.2010 um 01:35 schrieb Russell Keith-Magee: > >>> On Sun, Jul 11, 2010 at 10:36 AM, Antoni Aloy <antoni.a...@gmail.com> wrote: >>>> Hi, >>>> >>>> I have confirmed the bug with other non speaking people and I have >>>> sent an e-mail to django-i18n group to point out the problem. >>>> >>>> I have also contacted Marc and he has confirmed that the problem exists. >>>> >>>> Sorry for the insistence but in my opinion this is a blocker bug. >> >> On Tue, Jul 13, 2010 at 4:01 AM, Horst Gutmann <ze...@zerokspot.com> wrote: >>> Did the patch that is attached to this issue work for you? It would >>> really be nice to get some feedback on it :-) From what I've heard in >>> other posts on this and the django-users list so far it seems to do >>> the job. >> >> Ok - I'll put this on my list of things to look at. I've been fairly >> busy at work over the last couple of weeks, and what time I've had >> left has been consumed keeping feature discussions going. Once things >> settle down, I'll have more time to put into bugs. > > FYI, I planned to have a look at it this week, too. > > Jannis >
With the help of Jannis I fixed and simplified the patch at EuroPython and afterwards. The latest version (available in the ticket and on https://gist.github.com/ef8bce46d233c81df9d5 ) includes a change to the admin formfield generator. In my opinion, if USE_L10N=True, formfields should receive the localize=True flag by default for the admin. Would this be an acceptable change? Thank you :-) -- 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.
