#14807: django.utils.formats localize_input inserts thousands_separator into
boolean values
-------------------------------------+-------------------------------------
Reporter: vanschelven | Owner: nobody
Type: Uncategorized | Status: new
Component: | Version: 1.2
Internationalization | Resolution:
Severity: Normal | Triage Stage: Ready for
Keywords: | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by klaas@…):
* status: closed => new
* severity: => Normal
* type: => Uncategorized
* easy: => 0
* ui_ux: => 0
* resolution: fixed =>
Comment:
When fixing this, input_localize was missed. My proposed solution (which
is unfortunately not formatted as a pull request, nor does it have tests)
is here:
https://github.com/vanschelven/django/commit/f0e39c83ec9174b8e5241caa6ba59b8e2e6deb66
Also copying my notes from that solution to justify reopening the issue:
6c53a81 only fixed localize(), but not localize_input()
It appears to me that this was simply an oversight at the time.
It seems that a new call-order for fields somewhere between Django 1.4
and Django 1.6 triggers triggers this bug again, but this time on the
inputs
and only when rendering fields as_hidden.
--
Ticket URL: <https://code.djangoproject.com/ticket/14807#comment:7>
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/069.8a932e13e0820bca2748edda41cddb8b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
