#25762: Optimize numberformat.format
--------------------------------------+------------------------------------
Reporter: jaap3 | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Utilities | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by jaap3):
By the way, while refactoring this code I was wondering if supporting
NUMBER_GROUPING other than 3 is even useful. None of the locales shipped
with Django define anything other than 3, and the other related
configuration options (THOUSAND_SEPARATOR and USE_THOUSAND_SEPARATOR) all
refer to grouping by 3 anyway.
It would also be nice if number formatting on strings was deprecated. It
seems that Django already tries to call it with numbers in the places it's
used, and there's no real check if the strings that are passed into the
function are even number like.
--
Ticket URL: <https://code.djangoproject.com/ticket/25762#comment:3>
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/063.8db5e75bd136408a842af375e6e62320%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
