#5050: Better newforms metaclassing
---------------------------+------------------------------------------------
Reporter: SmileyChris | Owner: nobody
Status: new | Component: django.newforms
Version: SVN | Resolution:
Keywords: | Stage: Design decision needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------+------------------------------------------------
Comment (by mtredinnick):
This needs some django-dev discussion. I think the test case is not
necessarily a good goal because a lot of people are going to try to force
it to behave like Simon was expecting (the test looks like it's a
combination of two fields, even though if you remember it's Python you
realise it's just multiple inheritance).
I also feel a bit suspicious about the design. Both Form and !BaseForm end
up with the same root metaclass (because !DeclarativeFieldsMetaclass
inherits from !BaseFieldsMetaclass). I don't have a concrete reason why I
don't like that yet, but it smells funny. I can appreciate that mixins to
introduce common fields would be nice, but the implementation is fiddly.
If the goal is to shoehorn more tricks into form_for_*, I'm going to be a
hard sell.
--
Ticket URL: <http://code.djangoproject.com/ticket/5050#comment:10>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
