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 feature. If any application requires a specific integer representation, then they're outside the scope of localisation and their display should be coded specifically. On Oct 19, 6:33 am, Michel Thadeu Sabchuk <miche...@gmail.com> wrote: > > 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 inappropriate to display an Australian postcode > > withlocalize=True -- as "6,105", rather than "6105". -- 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.
