Hi Russel! > > While I digging to find the bug, I see that the DecimalField (and even > > the Field class) uses a "localize" attribute. I think this localize > > attribute is useless and I not alone: > > Well, no - it isn't useless. It was introduced for a very specific reason. > > Even if you are using L10N, there are occasions when localized widgets > *aren't* the right thing to do.
I agree with your arguments. Thanks for clarifying me! > That said, I will completely agree that it's inconvenient to need to > manually turn on localization everywhere. To that end, I'm interested > in any proposal that will: > > * make it easier to turn on form localization > * turn on form localization in admin. I need to dig some more to understand how exactly localization works and find a better approach (if needed) to set it on a field. Best regards! Michel Sabchuk -- 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.
