#36194: add async support to ManyToManyField
-----------------------------+--------------------------------------
     Reporter:  amirreza     |                    Owner:  amirreza
         Type:  New feature  |                   Status:  closed
    Component:  Forms        |                  Version:  5.1
     Severity:  Normal       |               Resolution:  wontfix
     Keywords:               |             Triage Stage:  Unreviewed
    Has patch:  0            |      Needs documentation:  0
  Needs tests:  0            |  Patch needs improvement:  0
Easy pickings:  1            |                    UI/UX:  0
-----------------------------+--------------------------------------
Changes (by Sarah Boyce):

 * resolution:   => wontfix
 * status:  assigned => closed

Comment:

 Thank you for the ticket!

 So, we haven't built-out async support for forms (yet).
 According to
 [https://github.com/django/deps/blob/main/accepted/0009-async.rst#forms
 DEP-9], we want to add async support for forms, and `ModelForm` in
 particular.

 The more recent conversation around whether
 [https://forum.djangoproject.com/t/is-dep009-async-capable-django-still-
 relevant/ DEP-9 is still relevant] discoraged async support being added to
 "everything".
 However, the components that were suggested as not worth the extra
 maintenance cost were [https://forum.djangoproject.com/t/is-dep009-async-
 capable-django-still-relevant/30132/2 Templates], and
 [https://forum.djangoproject.com/t/is-dep009-async-capable-django-still-
 relevant/30132/5 base admin views, the syndication framework, …]

 So I believe we could change this ticket title to "Async support for
 forms" and then can do multiple PRs to achieve this with `Refs #36194`

 I know that you are only talking about `ManyToManyField` here, however
 adding/updating the API to allow partial form support without discussing
 the wider goal for Django (to me) is not ideal.

 -------

 With all new features, we want to discuss with the community as to whether
 the change is desirable.

 In this case, I will add a message to the existing discussion and if we
 get a positive response (this can take a couple of weeks to assess), we
 can then accept the ticket.
 While we are understanding the ticket, it will be in the status "wontfix"
 and will stay this way unless/until we come to an agreement to action it.

 For more information, see
 [https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
 features/#requesting-features the documented guidelines for requesting
 features].
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36194#comment:4>
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 [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/django-updates/01070195130fb905-2ec65bce-e32b-4ec5-9922-31a754b554e8-000000%40eu-central-1.amazonses.com.

Reply via email to