#23795: Django form fields : limit_choices_to should not be mandatory with
queryset
-------------------------------------+-------------------------------------
Reporter: artscoop | Owner: nobody
Type: Bug | Status: closed
Component: Forms | Version: 1.7
Severity: Release blocker | Resolution: fixed
Keywords: formfield, | Triage Stage: Ready for
queryset, limit_choices_to | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Baptiste Mispelon <bmispelon@…>):
In [changeset:"606c57a132a1e1e680853c014efc41110ee75a80"]:
{{{
#!CommitTicketReference repository=""
revision="606c57a132a1e1e680853c014efc41110ee75a80"
[1.7.x] Fixed #23795 -- Fixed a regression in custom form fields
Custom form fields having a `queryset` attribute but no
`limit_choices_to` could no longer be used in ModelForms.
Refs #2445.
Thanks to artscoop for the report.
Backport of bfb11b95626f39e2f5e18d97d7761c6f93dcc1a9 from master.
Conflicts:
django/forms/fields.py
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23795#comment:6>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.d8d12b8ed443f7ab9563c424a4949615%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
