[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 -~----------~----~----~----~------~----~------~--~---
