On Mon, 2007-05-14 at 09:49 +0000, simonbun wrote: > What if we would make the 'decimal_places' argument illegal for the > new FloatField? That exception would make the change impossible to > miss. Hope I'm not missing anything obvious with this idea, it just > popped into my head.
Doh! Yes... that's the difference: it will break because that argument is no longer possible on a FloatField (it makes no sense for a true float) and it's compulsory in the current code. This is my punishment for worrying about a problem I didn't check existed. Okay. Problem solved. Nothing to see here. Everybody move along. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---