Bug: forms.DecimalField doesn't validate correctly when localized. (Unittest attached)

[Serge Spaolonzi]

forms.DecimalField doesn't validate correctly when localized.
A form DecimalField is expected to validate invalid values when the method to python is called.
It throws a ValidationError for non localized instances when an incorrect value is introduced.
But for localized instances that are expected to accept a comma (,) as decimal separator it doesn't throw any exception for a value with a dot (.) and take it as valid.

Unittest attached

[Aymeric Augustin]

The input isn't ambiguous: both "123.45" and "123,45" represent Decimal("123.45").

I don't see much value in rejecting the first form, especially Django historically accepts it. I would go as far as to say it isn't worth the backwards incompatibility.

[Claude Paroz]

I do agree with Aymeric. Unless we miss a problematic use case, I don't think this is an issue. Reopen if you can show us that this can cause bugs.

[libraM@…]

Quite neat IMHO, although for Django >= 1.6 only:

​https://docs.djangoproject.com/en/1.6/topics/forms/modelforms/#enabling-localization-of-fields
+
​https://docs.djangoproject.com/en/1.6/ref/contrib/admin/#django.contrib.admin.ModelAdmin.form