#2365: [patch] models.FloatField should be renamed
-------------------------------+--------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: defect | Status: new
Priority: normal | Milestone:
Component: Database wrapper | Version:
Severity: normal | Resolution:
Keywords: |
-------------------------------+--------------------------------------------
Comment (by mtredinnick):
I don't like the implication of the last paragraph of the previous
comment. It means that every single time you do arithmetic with this
field, you need to either test that you are running on Python 2.4 or call
float(). This is a huge burden on the developer. It has to work a bit more
transparently than that.
--
Ticket URL: <http://code.djangoproject.com/ticket/2365>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
