Commit 50020233 authored by Russell Keith-Magee's avatar Russell Keith-Magee
Browse files

[1.0.X] Fixed #11374 -- Modified the documentation for forms.BooleanField to...

[1.0.X] Fixed #11374 -- Modified the documentation for forms.BooleanField to allow for the fact that it can be rendered using widgets other than a checkbox. Thanks to lygaret for the patch.

Merge of r11236 from trunk.


git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@11243 bcc190cf-cafb-0310-a4f2-bffc1f526a37
parent ca3bd9ff
Loading
Loading
Loading
Loading
+22 −21
Original line number Diff line number Diff line
@@ -275,7 +275,7 @@ For each field, we describe the default widget used if you don't specify
    * Default widget: ``CheckboxInput``
    * Empty value: ``False``
    * Normalizes to: A Python ``True`` or ``False`` value.
    * Validates that the check box is checked (i.e. the value is ``True``) if
    * Validates that the value is ``True`` (e.g. the check box is checked) if
      the field has ``required=True``.
    * Error message keys: ``required``

@@ -287,9 +287,10 @@ For each field, we describe the default widget used if you don't specify
.. note::

    Since all ``Field`` subclasses have ``required=True`` by default, the
    validation condition here is important. If you want to include a checkbox
    in your form that can be either checked or unchecked, you must remember to
    pass in ``required=False`` when creating the ``BooleanField``.
    validation condition here is important. If you want to include a boolean
    in your form that can be either ``True`` or ``False`` (e.g. a checked or
    unchecked checkbox), you must remember to pass in ``required=False`` when
    creating the ``BooleanField``.

``CharField``
~~~~~~~~~~~~~