  
  These values are only displayed for unbound forms, and they're not used as
  fallback values if a particular value isn't provided.
  
  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::
  
      >>> class CommentForm(forms.Form):
      ...     name = forms.CharField(initial='class')
      ...     url = forms.URLField()
      ...     comment = forms.CharField()
 
</s> remove         :class:`datetime` value into a list with date and time split into two
        separate values::
 </s> add         :class:`~datetime.datetime` value into a list with date and time split
        into two separate values:: </s> remove * ``request.POST['choice']`` will raise :exc:`KeyError` if ``choice`` wasn't
  provided in POST data. The above code checks for :exc:`KeyError` and
  redisplays the poll form with an error message if ``choice`` isn't given.
 </s> add * ``request.POST['choice']`` will raise :exc:`~exceptions.KeyError` if
  ``choice`` wasn't provided in POST data. The above code checks for
  :exc:`~exceptions.KeyError` and redisplays the poll form with an error
  message if ``choice`` isn't given. </s> remove a :exc:`~django.db.DoesNotExist` exception when appropriate.
 </s> add a :exc:`~django.core.exceptions.DoesNotExist` exception when appropriate. </s> remove         :class:`~django.db.models.fields.BooleanField` on the model
 </s> add         :class:`~django.db.models.BooleanField` on the model </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.
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::
  
  These values are only displayed for unbound forms, and they're not used as
  fallback values if a particular value isn't provided.
  
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::
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::
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::
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::
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::
  
      >>> class CommentForm(forms.Form):
      ...     name = forms.CharField(initial='class')
      ...     url = forms.URLField()
      ...     comment = forms.CharField()
keep keep keep keep replace replace replace replace replace keep keep keep keep keep
 Fixed broken links, round 3. refs #19516 
docs/ref/forms/api.txt