Since Python 2.3 compatibility is an issue, per
ticket #3238, here are a couple possibilities:
(a) try/except import decimal and fall back to
float if decimal is not available.
(b) offer separate FloatField and a DecimalField
in newforms.
I'm -1 on (a) and +0 on (b). I find the decimal type
is useful for dealing with monetary values, but compared
to the other work being done on newforms, it's a
low priority issue (for me).
--
Jeff Bauer
Rubicon, Inc.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
