id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
27735	l10n is applied to Select widget's choices after template-based widget rendering	David Szotten	nobody	"While trying to update django-crispy-forms to django master (1.11) i came across the following:

on 1.10, 
Select (and e.g. RadioSelect, CheckboxSelectMultiple) don't seem to localise labels, but with template based widget rendering they do

(compare the output before and after template based widget rendering (e.g. 1.10 vs current master)

{{{
    settings.USE_L10N = True
    settings.USE_THOUSAND_SEPARATOR = True
    print forms.RadioSelect(choices=[(1000, 1000)]).render('foo', '1000')

    # master
    <option value=""1000"" selected>1,000</option>

    # 1.10
    <option value=""1000"" selected=""selected"">1000</option>
}}}


I've not been able to find documentation (my search-fu might be failing me) about either behaviour, (nor am i a user of l10n so i'm not sure which of these behaviours is more ""correct"")

so my question is: is this a regression? a bugfix?

(in https://github.com/django-crispy-forms/django-crispy-forms/issues/214#issuecomment-21688123 django-crispy-forms seems to choose its behaviour to match django, and adds explicit tests for the old behaviour)

Thanks"	Cleanup/optimization	closed	Documentation	dev	Release blocker	fixed			Ready for checkin	1	0	0	0	0	0