#28467: Missing real MultiValueField - MultiValueField is actually a MultiField
     Reporter:  Sven R. Kunze        |                    Owner:  nobody
         Type:                       |                   Status:  closed
  Cleanup/optimization               |
    Component:  Forms                |                  Version:  1.11
     Severity:  Normal               |               Resolution:  needsinfo
     Keywords:  MultiValueField      |             Triage Stage:
  MultiField                         |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
Changes (by Tim Graham):

 * status:  new => closed
 * resolution:   => needsinfo


 I think that usually a foreign key (and therefore, inline formsets) would
 be used for a one to many relation.

 Renaming `MultiValueField` would likely cause more disruption than its

 It's not clear to me how the field that you propose would be implemented.
 Feel free to implement something and share it to the
 DevelopersMailingList. If it becomes so popular that 80% of Django
 projects are using it, perhaps we would consider adding it to Django,
 however, I think the use case probably doesn't merit it. There are plenty
 of third-party apps providing useful form fields that don't need to be a
 part of Django itself.

Ticket URL: <https://code.djangoproject.com/ticket/28467#comment:2>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to