#14066 closed (invalid)
Shouldn't ModelFormMetaclass be public for inheritance issues?
Reported by: | rm4dillo | Owned by: | nobody |
---|---|---|---|
Component: | Core (Other) | Version: | 1.2 |
Severity: | Keywords: | ||
Cc: | && | Triage Stage: | Unreviewed |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Hi,
I'm trying to override the ModelForm class in order to create a Form with dynamic fields.
My new class (that inherits from ModelForm) needs a meta class which should be a child of ModelFormMetaclass but this class is not in the all list of the admin.forms.modules module.
Is there a reason for this? If not could you please add the ModelFormMetaclass symbol to admin.forms.modules._ _all_ _?
Thanks in advance.
Rm4dillo
Change History (3)
comment:1 by , 14 years ago
Cc: | added |
---|
comment:2 by , 14 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
You can still import it, _ _ all _ _ does not impose restrictions on importing.