Re: FloatField, localize and Django settings

2013-01-23 Thread Michael Anckaert
Thanks for your feedback. For reference, ticket is #19656 (
https://code.djangoproject.com/ticket/19656#ticket)


2013/1/22 Wim Feijen 

> Hi Michael, sounds very reasonable to me. Could you please file a bug
> ticket for that at https://code.djangoproject.com/newticket ?
>
>
> On Tuesday, 22 January 2013 21:30:09 UTC+1, Michael Anckaert wrote:
>
>> Hello everyone
>>
>> I came across an issue where my CBV and an automatic ModelForm gave me
>> some headaches with localization.
>>
>> The project is localized so a float is 3,2 instead of 3.2 (comma instead
>> of dot) but the CBV UpdateView didn't handle the localization of the float.
>> After tracking through the sources I noticed that the attribute localize
>> of FloatField has to be set manually.
>>
>> Wouldn't it be sensible to localize the FloatField according to the
>> project settings instead of having to manually set it in a custom form?
>>
>> Kind regards
>> Michael Anckaert
>> michael@sinax.be
>> http://www.sinax.be
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-developers/-/BFrsjaJD0hMJ.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>



-- 
Kind regards
Michael Anckaert 
http://www.sinax.be

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.



Re: FloatField, localize and Django settings

2013-01-22 Thread Wim Feijen
Hi Michael, sounds very reasonable to me. Could you please file a bug 
ticket for that at https://code.djangoproject.com/newticket ?

On Tuesday, 22 January 2013 21:30:09 UTC+1, Michael Anckaert wrote:
>
> Hello everyone
>
> I came across an issue where my CBV and an automatic ModelForm gave me 
> some headaches with localization. 
>
> The project is localized so a float is 3,2 instead of 3.2 (comma instead 
> of dot) but the CBV UpdateView didn't handle the localization of the float. 
> After tracking through the sources I noticed that the attribute localize 
> of FloatField has to be set manually. 
>
> Wouldn't it be sensible to localize the FloatField according to the 
> project settings instead of having to manually set it in a custom form? 
>
> Kind regards
> Michael Anckaert 
> michael@sinax.be 
> http://www.sinax.be 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/BFrsjaJD0hMJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.



FloatField, localize and Django settings

2013-01-22 Thread Michael Anckaert
Hello everyone

I came across an issue where my CBV and an automatic ModelForm gave me some
headaches with localization.

The project is localized so a float is 3,2 instead of 3.2 (comma instead of
dot) but the CBV UpdateView didn't handle the localization of the float.
After tracking through the sources I noticed that the attribute localize of
FloatField has to be set manually.

Wouldn't it be sensible to localize the FloatField according to the project
settings instead of having to manually set it in a custom form?

Kind regards
Michael Anckaert
michael.ancka...@sinax.be
http://www.sinax.be

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.