To add to the case, redefining fields in ModelForm can introduce serious problems and do more than just compromise DRY. E.g. if you have a model field that's optional (blank=True), you need not to forget to add 'required=False' to your form field re- declaration...
As for dynamic choices, I think that still belongs to the init method, not the Meta class. On Jul 6, 11:20 pm, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > Yuri Baburov wrote: > > And before it's landed into the trunk (i hope it will ;) ) you can > > make your own subclass of ModelForm which does exactly what you > > proposed, and then subclass it everywhere ;) > > Yuri, it's a bit redundant note :-). Sure everyone can subclass anything > or patch Django installation. I'm merely asking *if* it's sane enough to > be in Django itself. If yes I'm happy to make a patch. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
