django.contrib.humanize new filter (dotint)

[Wiliam Alves de Souza]

Converts an integer to a string containing dots every three digits. In Brazil we use dot not commas to separate numbers and is possible other location around the world use it too.

[Malcolm Tredinnick]

This is probably not the right approach for something in core. Rather, we should make the existing filter locale-aware when we put that stuff in (the plan is to include locale data for things like numeric separators and date formats). Then the existing filter will use dots or commas as appropriate for the page's locale.

So I'm -1 on this at the moment.

[Wiliam Alves de Souza]

Malcolm,
You think an approach like DATE_FORMAT, when each country has the possibility to change the default behavior of date format is the correct? What you think to create some options like NUMERIC, MONETARY, TELEPHONE and MEASUREMENT to be used internally for numeric separators, date formats, monetary values, telephone displaying and validation and measurement.

[finngruwier]

Replying to waa:

Converts an integer to a string containing dots every three digits. In Brazil we use dot not commas to separate numbers and is possible other location around the world use it too.

Same in many European locales. The dot is probably used in more locales then the comma.

[anonymous]

This issue definitely warrants some more attention in the long run, but how about doing something simple and effective for now (see attached diff). Would this make most people happy?

[erickd]

This issue definitely warrants some more attention in the long run, but how about doing something simple and effective for now (see attached diff). Would this make most people happy?

[Malcolm Tredinnick]

If people want something "for now", they are free to include this filter in their code; there is absolutely nothing requiring this to be part of Django. We are not in the habit of intentionally including half-baked solutions in the core code, however. It can wait for the full-scale solution, rather than having people write code using distributed Django that contains something which is already effectively end-of-lifed.

[Aymeric Augustin]

This feature is now provided by the THOUSAND_SEPARATOR and NUMBER_GROUPING — from the settings when USE_L10N = False, and each locale's formats.py when USE_L10N = True.

The values for pt_BRare correct:

THOUSAND_SEPARATOR = '.'
NUMBER_GROUPING = 3

All this probably didn't exist when the ticket was opened.