On Fri, 2009-08-07 at 08:37 -0700, gruszczy wrote: > Hi everyone! > > I have created a ticket here: http://code.djangoproject.com/ticket/11644, > but it was marked wontfix and told to ask here about this change. > > 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.
Russell's comments about it being an edge-case and particularly broken with respect to localization are key points here. The proposal cannot stand on its own without addressing those. In any case, I'm with Jacob and Russell on being a strong -1 here. It's a dozen extra characters of very standard Python if you want to do this in your own code. Not worth adding to Django's core, along with all the accompanying documentation and regression testing and maintenance. 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
