#2445: [patch] allow callable values for limit_choices_to
-------------------------------------+-------------------------------------
     Reporter:  michael@…            |                    Owner:  Tim
         Type:  New feature          |  Graham <timograham@…>
    Component:  Core (Other)         |                   Status:  closed
     Severity:  Normal               |                  Version:  master
     Keywords:  sprint2013           |               Resolution:  fixed
    Has patch:  1                    |             Triage Stage:  Accepted
  Needs tests:  0                    |      Needs documentation:  0
Easy pickings:  0                    |  Patch needs improvement:  0
                                     |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Baptiste Mispelon <bmispelon@…>):

 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/2445#comment:64>
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/079.bed270dd7177791b2d5f5a500f88b027%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to