Re: django.forms.fields.Field.localize to default to settings.USE_L10N

2011-02-16 Thread Simon Charette
Thank you very much for your feedback, I was wondering what were the edge cases that motivated such a decision. Do you believe it makes sense to have such a switch at the Form level, say a localize keyword which it's fields would default to? The same could apply to ModelAdmin localize_forms. If so

Re: django.forms.fields.Field.localize to default to settings.USE_L10N

2011-02-15 Thread Russell Keith-Magee
On Tue, Feb 15, 2011 at 9:37 AM, Simon Charette wrote: > Hi, I encountered a problem with DecimalField and DECIMAL_SEPARATOR in the > admin which lead me > to a ticket [1] which was marked as worksforme. > > Well it wasn't quite workingforme so I tried to come up with a testcase > since the ticket

django.forms.fields.Field.localize to default to settings.USE_L10N

2011-02-14 Thread Simon Charette
Hi, I encountered a problem with DecimalField and DECIMAL_SEPARATOR in the admin which lead me to a ticket [1] which was marked as worksforme. Well it wasn't quite workingforme so I tried to come up with a testcase since the ticket has none. I realised that the actual implementation of DecimalF