diff options
author | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2021-01-05 11:20:50 +0100 |
---|---|---|
committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2021-01-14 17:50:04 +0100 |
commit | b7dd89ed5389067cb70294682ffef1ba23d33934 (patch) | |
tree | 9d1cf97b9fda1ea8798cd543aee9d3f738a931f2 /docs/ref/forms | |
parent | 8774b1144c08f18e23381ffae7084dbc05ebfe37 (diff) | |
download | django-b7dd89ed5389067cb70294682ffef1ba23d33934.tar.gz |
Removed versionadded/changed annotations for 3.1.
Diffstat (limited to 'docs/ref/forms')
-rw-r--r-- | docs/ref/forms/api.txt | 2 | ||||
-rw-r--r-- | docs/ref/forms/fields.txt | 20 | ||||
-rw-r--r-- | docs/ref/forms/widgets.txt | 9 |
3 files changed, 0 insertions, 31 deletions
diff --git a/docs/ref/forms/api.txt b/docs/ref/forms/api.txt index 8bf8f3c9c1..5df969232a 100644 --- a/docs/ref/forms/api.txt +++ b/docs/ref/forms/api.txt @@ -974,8 +974,6 @@ Attributes of ``BoundField`` .. attribute:: BoundField.widget_type - .. versionadded:: 3.1 - Returns the lowercased class name of the wrapped field's widget, with any trailing ``input`` or ``widget`` removed. This may be used when building forms where the layout is dependent upon the widget type. For example:: diff --git a/docs/ref/forms/fields.txt b/docs/ref/forms/fields.txt index 9438214a28..52ab59e626 100644 --- a/docs/ref/forms/fields.txt +++ b/docs/ref/forms/fields.txt @@ -514,14 +514,6 @@ For each field, we describe the default widget used if you don't specify ``DATE_INPUT_FORMATS`` keys if localization is enabled. See also :doc:`format localization </topics/i18n/formatting>`. - .. versionchanged:: 3.1 - - Support for ISO 8601 date string parsing (including optional timezone) - was added. - - The fallback on ``DATE_INPUT_FORMATS`` in the default ``input_formats`` - was added. - ``DecimalField`` ---------------- @@ -782,8 +774,6 @@ For each field, we describe the default widget used if you don't specify .. class:: JSONField(encoder=None, decoder=None, **kwargs) - .. versionadded:: 3.1 - A field which accepts JSON encoded data for a :class:`~django.db.models.JSONField`. @@ -1450,21 +1440,11 @@ customize the yielded 2-tuple choices. :attr:`ChoiceField.choices`. The first ``value`` element is a :class:`ModelChoiceIteratorValue` instance. - .. versionchanged:: 3.1 - - In older versions, the first ``value`` element in the choice tuple - is the ``field`` value itself, rather than a - ``ModelChoiceIteratorValue`` instance. In most cases this proxies - transparently but, if you need the ``field`` value itself, use the - :attr:`ModelChoiceIteratorValue.value` attribute instead. - ``ModelChoiceIteratorValue`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. class:: ModelChoiceIteratorValue(value, instance) - .. versionadded:: 3.1 - Two arguments are required: .. attribute:: value diff --git a/docs/ref/forms/widgets.txt b/docs/ref/forms/widgets.txt index 9a19ab1436..dbcc9175d0 100644 --- a/docs/ref/forms/widgets.txt +++ b/docs/ref/forms/widgets.txt @@ -336,11 +336,6 @@ foundation for custom widgets. a hidden ``textarea`` element may want to always return ``False`` to avoid browser validation on the hidden field. - .. versionchanged:: 3.1 - - In older versions, ``True`` was returned for - :class:`~django.forms.FileInput` when ``initial`` was set. - ``MultiWidget`` --------------- @@ -372,10 +367,6 @@ foundation for custom widgets. >>> widget.render('name', ['john', 'paul']) '<input type="text" name="name" value="john"><input type="text" name="name_last" value="paul">' - .. versionchanged::3.1 - - Support for using a dictionary was added. - And one required method: .. method:: decompress(value) |