diff options
| author | Tim Graham <timograham@gmail.com> | 2016-05-20 10:50:51 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-05-20 11:44:29 -0400 |
| commit | 46a38307c245ab7ed0b4d5d5ebbaf523a81e3b75 (patch) | |
| tree | 214e952529a3d125d0efb097af9c4caa7e12635f /docs/ref/forms/api.txt | |
| parent | 1915a7e5c56d996b0e98decf8798c7f47ff04e76 (diff) | |
Removed versionadded/changed annotations for 1.9.
Diffstat (limited to 'docs/ref/forms/api.txt')
| -rw-r--r-- | docs/ref/forms/api.txt | 10 |
1 files changed, 0 insertions, 10 deletions
diff --git a/docs/ref/forms/api.txt b/docs/ref/forms/api.txt index c468dc38a0..9e9388344a 100644 --- a/docs/ref/forms/api.txt +++ b/docs/ref/forms/api.txt @@ -716,8 +716,6 @@ There are several other ways to customize the order: .. attribute:: Form.field_order -.. versionadded:: 1.9 - By default ``Form.field_order=None``, which retains the order in which you define the fields in your form class. If ``field_order`` is a list of field names, the fields are ordered as specified by the list and remaining fields are @@ -732,8 +730,6 @@ the ``Form``, then the latter ``field_order`` will have precedence. .. method:: Form.order_fields(field_order) -.. versionadded:: 1.9 - You may rearrange the fields any time using ``order_fields()`` with a list of field names as in :attr:`~django.forms.Form.field_order`. @@ -1013,8 +1009,6 @@ Methods of ``BoundField`` Customizing ``BoundField`` ========================== -.. versionadded:: 1.9 - If you need to access some additional information about a form field in a template and using a subclass of :class:`~django.forms.Field` isn't sufficient, consider also customizing :class:`~django.forms.BoundField`. @@ -1201,7 +1195,3 @@ The prefix can also be specified on the form class:: >>> class PersonForm(forms.Form): ... ... ... prefix = 'person' - -.. versionadded:: 1.9 - - The ability to specify ``prefix`` on the form class was added. |