Re: [Django] #7018: Make ModelForm multiple inheritance possible
Django
--------------------------------------------------+------------------------
Reporter: bear330 | Owner: nobody
Type: New feature | Status: new
Milestone: | Component: Forms
Version: SVN | Severity: Normal
Resolution: | Keywords:
Triage Stage: Design decision needed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------------------+------------------------
Changes (by semente):
* cc: semente+django@… (added)
* ui_ux: => 0
* easy: => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/7018#comment:15>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
---------------------------------------+------------------------
Reporter: bear330 | Owner: nobody
Type: New feature | Status: new
Milestone: | Component: Forms
Version: SVN | Severity: Normal
Resolution: | Keywords:
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
Changes (by Alex):
* stage: Design decision needed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/7018#comment:16>
Django
Reporter: bear330 | Owner: nobody
Type: New feature | Status: new
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by bouke):
* cc: bouke (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/7018#comment:17>
Django
-----------------------------+------------------------------------
Reporter: bear330 | Owner: nobody
Type: New feature | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
* cc: cyen0312+django@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/7018#comment:18>
Django
-----------------------------+------------------------------------
Reporter: bear330 | Owner: nobody
Type: New feature | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
* cc: maa@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/7018#comment:19>
Django
-----------------------------+------------------------------------
Reporter: bear330 | Owner: nobody
Type: New feature | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Comment (by mjtamlyn):
Worth noting here that you can now combine Form and ModelForm together.
Combining the multiple models is a much more complex issue, and one I'm
personally not convinced should be included. This has implications on
validation and saving which could have a myriad of edge cases. Personally
I think some code which renders and validates two forms would be superior,
handled effectively as a nonhomogeneous Form set.
--
Ticket URL: <https://code.djangoproject.com/ticket/7018#comment:20>
Django
-----------------------------+------------------------------------
Reporter: bear330 | Owner: nobody
Type: New feature | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Comment (by anonymous):
Replying to [comment:20 mjtamlyn]:
> Worth noting here that you can now combine Form and ModelForm together.
Combining the multiple models is a much more complex issue, and one I'm
personally not convinced should be included. This has implications on
validation and saving which could have a myriad of edge cases. Personally
I think some code which renders and validates two forms would be superior,
handled effectively as a nonhomogeneous Form set.
This is closer to what I want to do (combine multiple model forms in one
form)
Where can I find info on this ?
thanks,
--
Ticket URL: <https://code.djangoproject.com/ticket/7018#comment:21>
Django
-----------------------------+------------------------------------
Reporter: bear330 | Owner: nobody
Type: New feature | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Comment (by mjtamlyn):
Sounds like you want something along the lines of
https://github.com/bmispelon/django-multiform
You'd nerd to write the connection logic yourself each time but I think
that's fine. Personally I'm not convinced this is code which needs to live
in core. Baptiste may have a different opinion.
--
Ticket URL: <https://code.djangoproject.com/ticket/7018#comment:22>
Django
-----------------------------+------------------------------------
Reporter: bear330 | Owner: nobody
Type: New feature | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Comment (by mitar):
Now with Django 1.9, the approaches mentioned in this ticket do not work
anymore, because get_declared_fields is not available anymore. What would
be a new approach?
--
Ticket URL: <https://code.djangoproject.com/ticket/7018#comment:23>
Django
-----------------------------+------------------------------------
Reporter: bear330 | Owner: nobody
Type: New feature | Status: new
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
* cc: Mike Fogel (removed)
--
Ticket URL: <https://code.djangoproject.com/ticket/7018#comment:24>