In conclusion one could say that if USE_L10N is not True then no thousands separator is displayed, of course, only thru the configuration of django.
El viernes, 20 de diciembre de 2013 08:15:58 UTC-5, Yonel Ceruto González escribió: > > Ok no problem, > > Although the documentation may be inconsistent, I think the comment > https://code.djangoproject.com/ticket/21544 # comment: 8, discloses a > particular > case where I customize the THOUSAND_SEPARATOR with USE_L10N = False. This is > the source of my problem, because he expects to see the thousands > separator to the display the numbers. > > El jueves, 19 de diciembre de 2013 16:19:42 UTC-5, Shai Berger escribió: >> >> Hi, >> >> On Thursday 19 December 2013 05:25:11 Yonel Ceruto González wrote: >> > Forgive me if at some point was arrogant, it was not my intention to >> impose >> > my judgment or criticize, for me, the best framework that exists. Maybe >> I >> > was not regarded with good intentions and therefore I believe the >> answers >> > were focused to dodge my proposal.Most likely I knew not express well, >> beg >> > a thousand pardons. >> >> As the person who closed the ticket, your mail here indicates that I may >> have >> been too harsh, and I apologize for that. I would like to assure you that >> your >> intentions appear good, and your proposal was rejected purely on >> technical >> reasons, mostly according to the documentation of USE_THOUSAND_SEPARATOR >> and >> USE_L10N. >> >> However, having looked again, I now think that you do have a case -- >> while for >> the settings you pointed to, the documentation strongly implies the >> current >> behavior, the documentation for NUMBER_GROUPING and THOUSAND_SEPARATOR >> does >> support your interpretation (and in your first message you mentioned >> having set >> NUMBER_GROUPING=3). For both these settings, the documentation says: >> >> Note that if USE_L10N is set to True, then the locale-dictated >> format has >> higher precedence and will be applied instead. >> >> So -- to me, it looks like the documentation is not entirely consistent, >> and >> should be clarified; and while changing the behavior would be >> problematic, >> changing it to match (some) documentation should be a possibility. >> >> I'm waiting for other opinions -- in particular, anyone involved with the >> introduction of these settings, who can explain the original intentions >> -- to >> decide if we should reopen the ticket[1] as is or change it to a >> documentation >> ticket. >> >> Shai. >> >> [1] https://code.djangoproject.com/ticket/21544 >> > -- You received this message because you are subscribed to the Google Groups "Django developers" 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]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/a1cfc902-9284-4c68-9c70-35f9516c6e48%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
