#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
-------------------------------------+-------------------------------------
Changes (by Baptiste Mispelon <bmispelon@…>):

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


Comment:

 In [changeset:"bfb11b95626f39e2f5e18d97d7761c6f93dcc1a9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bfb11b95626f39e2f5e18d97d7761c6f93dcc1a9"
 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.
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/23795#comment:5>
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.8b21e0a48d3aa281c88c5d1f36c6c185%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to