On Nov 8, 4:30 am, "Marty Alchin" <[EMAIL PROTECTED]> wrote: > When you pass in a subclass of Form, it's already got its fields in > the right place, but more importantly, it triggers that syntax > checking again, where it looks for new fields. It basically copies > fields from a parent class, then adds in the fields that it found in > the new class. However, since form_for_model and form_for_instance > don't supply any fields that way, all it gives the new form is what it > found in the parent class, completely overwriting the fields it got > from form_for_*.
Actually, I see no good reason why you shouldn't be able to use a Form as the SuperClass of your form_for_* form. I've just attached a patch to #3815 which makes it work. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---