#31262: Support dictionaries in Field.choices for named groups.
-------------------------------------+-------------------------------------
     Reporter:  Tom Forbes           |                    Owner:  Nick Pope
         Type:  New feature          |                   Status:  closed
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by GitHub <noreply@…>):

 In [changeset:"8c8cbe66fa4354a3c50e4f5f248fcf5fd597e724" 8c8cbe66]:
 {{{
 #!CommitTicketReference repository=""
 revision="8c8cbe66fa4354a3c50e4f5f248fcf5fd597e724"
 Refs #31262 -- Renamed ChoiceIterator to BaseChoiceIterator.

 Some third-party applications, e.g. `django-filter`, already define
 their own `ChoiceIterator`, so renaming this `BaseChoiceIterator` will
 be a better fit and avoid any potential confusion.

 See https://github.com/carltongibson/django-filter/pull/1607.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31262#comment:16>
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 on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018a600d8e8d-feee441a-805a-40e7-8072-0eb140739a4f-000000%40eu-central-1.amazonses.com.

Reply via email to