  -----------------------------
  
  Many widgets have optional extra arguments; they can be set when defining the
  widget on the field. In the following example, the
  :attr:`~SelectDateWidget.years` attribute is set for a
  :class:`~django.forms.extras.widgets.SelectDateWidget`::
  
      from django.forms.fields import DateField, ChoiceField, MultipleChoiceField
      from django.forms.widgets import RadioSelect, CheckboxSelectMultiple
      from django.forms.extras.widgets import SelectDateWidget
  
 
</s> remove     If one of your views receives an :class:`HttpRequest` object with
    :attr:`POST parameters<HttpRequest.POST>` susceptible to contain sensitive
    information, you may prevent the values of those parameters from being
    included in the error reports using the ``sensitive_post_parameters``
    decorator::
 </s> add     If one of your views receives an :class:`~django.http.HttpRequest` object
    with :attr:`POST parameters<django.http.HttpRequest.POST>` susceptible to
    contain sensitive information, you may prevent the values of those
    parameters from being included in the error reports using the
    ``sensitive_post_parameters`` decorator:: </s> remove     The intermediate model class describing the :class:`ManyToManyField`.
    This class is automatically created when a many-to-many field is
    defined; you can access it using the ``through`` attribute on the
    many-to-many field.
 </s> add     The intermediate model class describing the
    :class:`~django.db.models.ManyToManyField`. This class is automatically
    created when a many-to-many field is defined; you can access it using the
    ``through`` attribute on the many-to-many field. </s> remove         :class:`~django.db.models.fields.DateField` or
        :class:`~django.db.models.fields.DateTimeField` on the model for which
 </s> add         :class:`~django.db.models.DateField` or
        :class:`~django.db.models.DateTimeField` on the model for which </s> remove Note that if a :class:`~django.forms.fields.Field` defines
:attr:`~Form.initial` *and* you include ``initial`` when instantiating the
``Form``, then the latter ``initial`` will have precedence. In this example,
``initial`` is provided both at the field level and at the form instance level,
and the latter gets precedence::
 </s> add Note that if a :class:`~django.forms.Field` defines :attr:`~Form.initial` *and*
you include ``initial`` when instantiating the ``Form``, then the latter
``initial`` will have precedence. In this example, ``initial`` is provided both
at the field level and at the form instance level, and the latter gets
precedence:: </s> remove a :exc:`~django.db.DoesNotExist` exception when appropriate.
 </s> add a :exc:`~django.core.exceptions.DoesNotExist` exception when appropriate.
:attr:`~django.forms.extras.widgets.SelectDateWidget.years` attribute is set
for a :class:`~django.forms.extras.widgets.SelectDateWidget`::
  -----------------------------
  
  Many widgets have optional extra arguments; they can be set when defining the
  widget on the field. In the following example, the
:attr:`~django.forms.extras.widgets.SelectDateWidget.years` attribute is set
for a :class:`~django.forms.extras.widgets.SelectDateWidget`::
:attr:`~django.forms.extras.widgets.SelectDateWidget.years` attribute is set
for a :class:`~django.forms.extras.widgets.SelectDateWidget`::
  
      from django.forms.fields import DateField, ChoiceField, MultipleChoiceField
      from django.forms.widgets import RadioSelect, CheckboxSelectMultiple
      from django.forms.extras.widgets import SelectDateWidget
  
keep keep keep keep replace replace keep keep keep keep keep
 Fixed broken links, round 3. refs #19516 
docs/ref/forms/widgets.txt