Jacob Kaplan-Moss wrote: > On 10/26/06 2:49 AM, Christopher Lenz wrote: > > Oh come on, just let Python 2.3 users install the decimal module from > > SF: > > > > <http://sourceforge.net/project/showfiles.php? > > group_id=104148&package_id=130611&release_id=291663> > > > > I'd also suggest keeping FloatField as it is (i.e. half-broken, > > depending on DB backend, or fix it to always return floats, but > > that's break backwards compatibility again), deprecate it, and > > introduce the new DecimalField. Only the use of DecimalField would > > require the decimal.py module, same as ImageField requires PIL. > > Yeah, this sounds like a very good idea. Doesn't break existing code, doesn't > require decimal.py if floats are OK. I'm +1 on this - any objections?
+1 too. I think we should fix FloatField to use the correct type in the DB backend though (and document possible backwards-incompatibilities) - it's a shame to leave it half-broken before a 1.0 release. Jason --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
