diff options
| author | Tim Graham <timograham@gmail.com> | 2012-12-25 09:56:22 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2012-12-26 19:07:22 -0500 |
| commit | b3a8c9dab87be6bc4b8096d292abe0b35c700bdd (patch) | |
| tree | f48e2778028ef3c147d688b168f374b9d6dabd26 /docs/ref/forms | |
| parent | e2ec7b47b3acb0338d971942ca7ffd36c2a4d8f4 (diff) | |
Fixed broken links, round 3. refs #19516
Diffstat (limited to 'docs/ref/forms')
| -rw-r--r-- | docs/ref/forms/api.txt | 10 | ||||
| -rw-r--r-- | docs/ref/forms/fields.txt | 2 | ||||
| -rw-r--r-- | docs/ref/forms/widgets.txt | 10 |
3 files changed, 11 insertions, 11 deletions
diff --git a/docs/ref/forms/api.txt b/docs/ref/forms/api.txt index dffef314b7..ab1f4b0eea 100644 --- a/docs/ref/forms/api.txt +++ b/docs/ref/forms/api.txt @@ -150,11 +150,11 @@ it's not necessary to include every field in your form. For example:: 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:: +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') diff --git a/docs/ref/forms/fields.txt b/docs/ref/forms/fields.txt index 75d05c6829..c7d9c5fbbe 100644 --- a/docs/ref/forms/fields.txt +++ b/docs/ref/forms/fields.txt @@ -885,7 +885,7 @@ Slightly complex built-in ``Field`` classes .. attribute:: MultiValueField.widget Must be a subclass of :class:`django.forms.MultiWidget`. - Default value is :class:`~django.forms.widgets.TextInput`, which + Default value is :class:`~django.forms.TextInput`, which probably is not very useful in this case. .. method:: compress(data_list) diff --git a/docs/ref/forms/widgets.txt b/docs/ref/forms/widgets.txt index a0ef0731ad..0660329eea 100644 --- a/docs/ref/forms/widgets.txt +++ b/docs/ref/forms/widgets.txt @@ -49,8 +49,8 @@ Setting arguments for widgets 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`:: +: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 @@ -222,7 +222,7 @@ foundation for custom widgets. .. class:: MultiWidget(widgets, attrs=None) A widget that is composed of multiple widgets. - :class:`~django.forms.widgets.MultiWidget` works hand in hand with the + :class:`~django.forms.MultiWidget` works hand in hand with the :class:`~django.forms.MultiValueField`. :class:`MultiWidget` has one required argument: @@ -246,8 +246,8 @@ foundation for custom widgets. the combined value of the form field into the values for each widget. An example of this is how :class:`SplitDateTimeWidget` turns a - :class:`datetime` value into a list with date and time split into two - separate values:: + :class:`~datetime.datetime` value into a list with date and time split + into two separate values:: class SplitDateTimeWidget(MultiWidget): |
