That's probably a poor example. Australian postcodes should be a
StringField with a validation constraint ensuring that its 4 digits.
Why? Well, there are australian postcodes that start with 0 - Northern
Territory - and they're not going to be displayed correctly with ANY
reasonable localisation
Hi Russell!
> Even if you are using L10N, there are occasions when localized widgets
> *aren't* the right thing to do.
>
> Consider as an example: Australian postcodes are 4 digit numbers. It's
> entirely reasonable that they might be stored as an IntegerField. But
> it would be completely inappro
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
On Sat, Oct 9, 2010 at 2:25 AM, Michel Thadeu Sabchuk
wrote:
> 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 DecimalFi
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 lo
