On 12/26/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
The issue of having "real" floats, in some sense still remains on the table because we have made an unfortunate naming choice: FloatField is a fixed-point (i.e. Python decimal) field, so what do we use for a real float field.
I'm pretty sure I've seen a disclaimer somewhere saying that there might be incompatible changes for 1.0. Why not just rename it now while you have a chance? Doing a find and replace on FloatField shouldn't be so hard for Django developers. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
