#22654: DecimalField and DECIMAL_SEPARATOR (in admin)
--------------------------+-----------------------------------------
Reporter: matija@… | Owner:
Type: Bug | Status: new
Component: Forms | Version: 1.6
Severity: Normal | Resolution:
Keywords: | Triage Stage: Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------+-----------------------------------------
Comment (by matija@…):
Ok, I got it.
This is definitely a design problem. Date/Datetime settings work
regardless of L10N, and Decimal-related only when L10N is set.
(sanitize_separators checks L10N first).
These two things are closely related and should follow the same logic.
IMHO the key question is should Dates AND Dacimals (and other L10N-related
stuff) follow DATE_FORMATS, DECIMAL_SEPARATOR and other L10N related
setting when L10N is False. The answer should be Yes or No for all of
them.
Yes, I do get a comma in the output. However, on re-saving, errors are
shown. If I replace it with a dot, it works, and comma is shown in
response.
--
Ticket URL: <https://code.djangoproject.com/ticket/22654#comment:8>
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/077.667c0e1d96cbba8fea2135c9b0608aad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
