On Tue, 2007-05-08 at 17:44 -0400, Andy Dustman wrote:
> On 5/2/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> > I'm going to work on that problem (putting in decimal support) this week
> > sometime. Maybe today or tomorrow. It's starting to annoy me, seeing all
> > the decimal-reated
On 5/8/07, Andy Dustman <[EMAIL PROTECTED]> wrote:
> Perhaps Django needs a
> DecimalField (or NumericField) for fixed-point values? (You might be
> working on this; haven't searched bugs.)
This has been discussed before and, so far as I can tell, is an active
topic of discussion ('Design
On 5/2/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> I'm going to work on that problem (putting in decimal support) this week
> sometime. Maybe today or tomorrow. It's starting to annoy me, seeing all
> the decimal-reated tickets in Trac, so after I knock off all the email
> ones (today),
On Tue, 2007-05-01 at 16:28 -0400, Andy Dustman wrote:
> On 5/1/07, Chris Brand <[EMAIL PROTECTED]> wrote:
> >
> > I've got a model that includes FloatFields as well as IntegerFields and
> > CharFields.
> > When I access the CharFields, I get strings. When I access the
> > IntegerFields, I get
> What version of Python are you using? I *think* FloatFields are
> returned as Python Decimal objects, which don't exist before
> Python-2.4, which means you would then get a string from MySQLdb. We
> might need a fix for Django on Python-2.3 to work around this.
"python -V" reports "Python
On 5/1/07, Chris Brand <[EMAIL PROTECTED]> wrote:
>
> I've got a model that includes FloatFields as well as IntegerFields and
> CharFields.
> When I access the CharFields, I get strings. When I access the
> IntegerFields, I get integers, but when I want to use the Floatfields, I
> always have to
6 matches
Mail list logo
