Is there any thought on decoupling the "choices" parameter from the
type of bound Field, so that for instance something like
IntegerField('Results per page', choices=[(n,n) for n in
10,20,30,50,100])
would work as expected and not return string instead ? If not, I'll add
a ticket, though I'm not sure if it should be filed as an enhancement
or a bug; certainly the current behaviour is surprising, to say the
least.
Thanks,
George
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
