#28345: limit_choices_to callable is no longer applied during ModelForm
instantiation which blocks some use cases
---------------------------------+----------------------------------------
Reporter: drunkard | Owner: Jon Dufresne
Type: Bug | Status: assigned
Component: Forms | Version: 1.11
Severity: Release blocker | Resolution:
Keywords: ModelForm | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+----------------------------------------
Comment (by Jon Dufresne):
[https://github.com/django/django/pull/8687 PR]
The change adds an additional keyword argument, `apply_limit_choices_to`,
to `field_for_model()`. This arugment allows `field_for_model()` to
continue to be used to create form fields dynamically after
`ModelForm.__init__()` is called.
--
Ticket URL: <https://code.djangoproject.com/ticket/28345#comment:3>
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
https://groups.google.com/d/msgid/django-updates/066.70c49c7ff9d9caa7195321e8f37231c8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
