Hi guys, how are you? I had problems with DecimalField and localize input/output. I found the bug and I'm working on it:
http://code.djangoproject.com/ticket/14101 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: http://groups.google.com/group/django-developers/browse_thread/thread/68d2f628bca73e4d/5b576a1f9f4a32ed?lnk=gst&q=localize#5b576a1f9f4a32ed The localize attribute controls the usage of the formats methods like sanitize_separators or number_format. Reather than control it with a keyword argument for the field class, we should use the USE_L10N setting. But the formats methods already check it, so we can just call the methods on the field class, without bother is USE_L10N is on or off. What do you think? Can I create a ticket for it? Best regards! -- 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.
