On Fri, Aug 7, 2009 at 10:37 AM, gruszczy<[email protected]> wrote:
> The issue is that I consider convenient being able to pass a list of
> either tuples or single objects for choices list in forms ChoiceField.
> The engine would itself detect non-tuple values and turn them into two-
> tuples. There are some good points in the comment (like lacking
> documentation/tickets, which I would gladly provide), but first I
> would like to ask, if such a feature would be acceptable, just like
> the advice in the comment suggested.
Frankly I don't see the point.
What does::
f = CharField(choices=LIST)
have over::
f = CharField(choices=zip(LIST, LIST))
?
Jacob
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
