#19656: FloatField localization
-------------------------------------+-------------------------------------
Reporter: michael.anckaert@… | Owner: nobody
Type: New feature | Status: closed
Component: Forms | Version: 1.4
Severity: Normal | Resolution: duplicate
Keywords: FloatField | Triage Stage:
Localization | Unreviewed
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by claudep):
* status: new => closed
* resolution: => duplicate
Comment:
Read #13032 to understand why `localize` is False by default. Defaulting
to True for `FloatField` only would not be a consistent behaviour.
#13546 discusses `localize` issues related to ModelForms, I'd suggest you
contribute to that discussion.
Somewhat related is #16612, a bug with changed detection of localized
values in some fields.
--
Ticket URL: <https://code.djangoproject.com/ticket/19656#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
