My understanding is that the best way to have the choices in a choice field to update dynamically is to subclass form and override __init__().
Is this still the case? I'm coming from TurboGears, which has a very similar form/widget/ validation system. But one nice feature in TG is that you can pass an "options" dictionary when instantiating a form, in which the key is the field in the form and the value is a list of tuples specifying the current options for that field. Would this be a good idea for Django newforms? It seems a common enough need. e.g. right now I have a ChoiceField on one form in which the user selects a location, and when they submit that it needs to bring up another form with another choice field whose options depend upon the location. -Steve --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
