Thanks for your replies. Regarding the localize option, I tried to use it in my models.py [1].
However, I get the following error. Field.__init__(self, verbose_name, name, **kwargs) TypeError: __init__() got an unexpected keyword argument 'localize' [1] http://pastebin.com/9TkwWnNY Can localize only be used for forms but not for my models that are eventually represented in the admin backend form? Robert On May 3, 8:21 am, jrief <[email protected]> wrote: > Internally a price is always handled and stored as 0.00. Thats the way > software and databases work. > > What you can do is to change the representation of your Decimal in your > frontend and backend. In Django, changing this in the frontend its easy, > just add USE_L10N = True to your settings.py and add localized=True to all > occurrences of form fields handling a Decimal > (seehttps://docs.djangoproject.com/en/1.4/ref/forms/fields/#localize) > > The problem is the backend, because you are not specifying these form > field. What I do is to add a mixin class to my admin classes, as described > here:https://github.com/divio/django-shop/pull/146#issuecomment-4720340 > and > herehttps://github.com/divio/django-shop/blob/master/shop/admin/mixins.py > > For your "2.1" problem, set decimal_places to 2 DecimalField. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
