Removed versionadded/changed annotations for 1.9.

4 files changed, 0 insertions, 41 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.
diff --git a/docs/ref/forms/fields.txt b/docs/ref/forms/fields.txt
index b81dbef61c..13b937b117 100644
--- a/docs/ref/forms/fields.txt
+++ b/docs/ref/forms/fields.txt
@@ -305,8 +305,6 @@ more information.
 
 .. attribute:: Field.disabled
 
-.. versionadded:: 1.9
-
 The ``disabled`` boolean argument, when set to ``True``, disables a form field
 using the ``disabled`` HTML attribute so that it won't be editable by users.
 Even if a user tampers with the field's value submitted to the server, it will
@@ -379,8 +377,6 @@ For each field, we describe the default widget used if you don't specify
 
     .. attribute:: strip
 
-       .. versionadded:: 1.9
-
        If ``True`` (default), the value will be stripped of leading and
        trailing whitespace.
 
@@ -834,8 +830,6 @@ For each field, we describe the default widget used if you don't specify
 
     .. attribute:: strip
 
-        .. versionadded:: 1.9
-
         Defaults to ``False``. If enabled, stripping will be applied before the
         regex validation.
 
@@ -858,8 +852,6 @@ For each field, we describe the default widget used if you don't specify
 
    .. attribute:: allow_unicode
 
-       .. versionadded:: 1.9
-
        A boolean instructing the field to accept Unicode letters in addition
        to ASCII letters. Defaults to ``False``.
 
diff --git a/docs/ref/forms/models.txt b/docs/ref/forms/models.txt
index 1fa2e958ad..c5ddf99011 100644
--- a/docs/ref/forms/models.txt
+++ b/docs/ref/forms/models.txt
@@ -49,10 +49,6 @@ Model Form API reference. For introductory material about model forms, see the
     information. Omitting any definition of the fields to use will result in
     an :exc:`~django.core.exceptions.ImproperlyConfigured` exception.
 
-    .. versionadded:: 1.9
-
-        The ``field_classes`` keyword argument was added.
-
 ``modelformset_factory``
 ========================
 
@@ -72,10 +68,6 @@ Model Form API reference. For introductory material about model forms, see the
 
     See :ref:`model-formsets` for example usage.
 
-    .. versionadded:: 1.9
-
-        The ``field_classes`` keyword argument was added.
-
 ``inlineformset_factory``
 =========================
 
@@ -89,7 +81,3 @@ Model Form API reference. For introductory material about model forms, see the
     the ``parent_model``, you must specify a ``fk_name``.
 
     See :ref:`inline-formsets` for example usage.
-
-    .. versionadded:: 1.9
-
-        The ``field_classes`` keyword argument was added.
diff --git a/docs/ref/forms/widgets.txt b/docs/ref/forms/widgets.txt
index 88ac06903c..850905fb40 100644
--- a/docs/ref/forms/widgets.txt
+++ b/docs/ref/forms/widgets.txt
@@ -223,11 +223,6 @@ foundation for custom widgets.
        microseconds part of :class:`~datetime.datetime` and
        :class:`~datetime.time` values will be set to ``0``.
 
-       .. versionadded:: 1.9
-
-           In older versions, this attribute was only defined on the date
-           and time widgets (as ``False``).
-
     .. method:: format_value(value)
 
         Cleans and returns a value for use in the widget template. ``value``
@@ -843,9 +838,3 @@ Composite widgets
                     empty_label=("Choose Year", "Choose Month", "Choose Day"),
                 ),
             )
-
-    .. versionchanged:: 1.9
-
-        This widget used to be located in the ``django.forms.extras.widgets``
-        package. It is now defined in ``django.forms.widgets`` and like the
-        other widgets it can be imported directly from ``django.forms``.