Yes, now I understand. You are doing form_for_model. That is certainly an issue with the newforms library, likely due to the fact that it is not finished. For now, you might do what I suggested, or write a patch to build that functionality into newforms.
On Jan 25, 12:39 am, "ak" <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED], either you don't understand me or I don't > understand you. > > > I misspoke earlier. I said you could specify a Select widget for a > > CharField to get that output. I don't know if that will actually work > > (you could try it) > > > field3 = CharField(widget=Select(choices=<tuple of choices>))Yes BUT I was > > talking about behavior of oldforms. When I define a > CharField in model with choices=(...), it automatically converted to > <input type="select">, not to <input type="text"> So I didn't need to > specify choices twice: in model and in views. > So I don't think that your suggestion is a complex solution. Do you see > ? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
