[Django] #37194: Update Choice widget documentation to reflect current class heirarchy

[Django]

#37194: Update Choice widget documentation to reflect current class heirarchy
-----------------------------+-----------------------------------------
Reporter: David Smith | Type: Uncategorized
Status: new | Component: Documentation
Version: 6.0 | Severity: Normal
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+-----------------------------------------
The documentation has a section called "Widgets inheriting from the
`Select` widget", see
[https://docs.djangoproject.com/en/6.1/ref/forms/widgets/#widgets-
inheriting-from-the-select-widget docs]. It then goes on to talk about
choice widgets including both `Select` and `RadioSelect` inputs.

Since 9ac4dbd7b53d187ca54f28e247d3a120660938ca not all choice widgets
inherit from the `Select` widget. Currently, both `Select` and
`RadioSelect` are subclasses of the undocumented `ChoiceWidget`.

I've drafted a possible patch for discussion

{{{
Widgets with choices
====================

There are a group of widgets which deal with choices and present the user
with
a list of options to choose from. The different widgets present this
choice
differently; the :class:`Select` widget uses a ``<select>`` HTML list
representation, while :class:`RadioSelect` uses radio buttons and
:class:`CheckboxSelectMultiple` uses checkboxes.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/37194>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#37194: Update Choice widget documentation to reflect current class heirarchy

--------------------------------------+------------------------------------
Reporter: David Smith | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 6.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted

Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0

--------------------------------------+------------------------------------
Changes (by Natalia Bidart):

* stage: Unreviewed => Accepted
* type: Uncategorized => Cleanup/optimization

Comment:

Sounds good, thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/37194#comment:1>