intcomma now (incorrectly) requires USE_THOUSAND_SEPARATOR = True

[anonymous]

Prior to r16168, the django.contrib.humanize intcomma filter, when used in a project with settings:

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.

[Bas Peschier]

Marked #16558 as a duplicate as it describes a symptom.

[Malcolm Tredinnick]

Looks like a dupe of #16404.