http://code.djangoproject.com/ticket/16015
I've uploaded a patch, but changed the status to 'Design Decision Needed'
from 'Accepted.'
The problem is that although my patch follows the existing convention and
results in passing tests in Python 2.6, the Python core developers have made
an import
On 05/12/2011 08:04 PM, Russell Keith-Magee wrote:
I suspect the answer will lie somewhere between get_prep_value() and
to_python() on DecimalField, but you'll need to do some code path
tracing to confirm. Looking at the code, I'm a little surprised that
it doesn't work as is...
Yours,
Russ Mag
On Fri, May 13, 2011 at 12:08 AM, Shawn Milochik wrote:
> On 05/11/2011 08:00 PM, Russell Keith-Magee wrote:
>>
>> On Thu, May 12, 2011 at 3:35 AM, Shawn Milochik
>> wrote:
>>>
>>> Someone on django-users just commented that they set a default value on a
>>> DecimalField as a float, and were surp
On 05/11/2011 08:00 PM, Russell Keith-Magee wrote:
On Thu, May 12, 2011 at 3:35 AM, Shawn Milochik wrote:
Someone on django-users just commented that they set a default value on a
DecimalField as a float, and were surprised when they were unable to create
a queryset using a float to find record
On Thu, May 12, 2011 at 3:35 AM, Shawn Milochik wrote:
> Someone on django-users just commented that they set a default value on a
> DecimalField as a float, and were surprised when they were unable to create
> a queryset using a float to find records.
>
> I searched Trac for the terms 'DecimalFie
Someone on django-users just commented that they set a default value on
a DecimalField as a float, and were surprised when they were unable to
create a queryset using a float to find records.
I searched Trac for the terms 'DecimalField default' and didn't see
anywhere that this was brought up
