#16562: intcomma now (incorrectly) requires USE_THOUSAND_SEPARATOR = True
-----------------------+----------------------------------
Reporter: anonymous | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: contrib.humanize
Version: SVN | Severity: Release blocker
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------+----------------------------------
Prior to r16168, the `django.contrib.humanize` intcomma filter, when used
in a project with settings:
{{{
#!python
USE_L10N = True
USE_THOUSAND_SEPARATOR = False
LANGUAGE_CODE = 'en-us'
}}}
would insert commas into numbers. After r16168, intcomma requires that
USE_THOUSAND_SEPARATOR = True in order for it to insert the commas (or
other separator for other languages, I'd guess). This is a regression and
a bit non-sensical: if I'm specifically coding intcomma into my templates,
it's a safe bet I do want the commas added, regardless of the
USE_THOUSAND_SEPARATOR setting.
--
Ticket URL: <https://code.djangoproject.com/ticket/16562>
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 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-updates?hl=en.
