Removed versionadded/changed annotations for 4.0.

This commit is contained in:
Carlton Gibson 2022-05-10 15:07:11 +02:00 committed by Carlton Gibson
parent d10e569ea5
commit ca1c3151c3
44 changed files with 0 additions and 316 deletions

View file

@ -529,8 +529,6 @@ attributes.
``template_name``
~~~~~~~~~~~~~~~~~
.. versionadded:: 4.0
.. attribute:: Form.template_name
The name of the template rendered if the form is cast into a string, e.g. via
@ -549,8 +547,6 @@ class.
``render()``
~~~~~~~~~~~~
.. versionadded:: 4.0
.. method:: Form.render(template_name=None, context=None, renderer=None)
The render method is called by ``__str__`` as well as the
@ -567,8 +563,6 @@ single call.
``get_context()``
~~~~~~~~~~~~~~~~~
.. versionadded:: 4.0
.. method:: Form.get_context()
Return the template context for rendering the form.
@ -583,8 +577,6 @@ The available context is:
``template_name_label``
~~~~~~~~~~~~~~~~~~~~~~~
.. versionadded:: 4.0
.. attribute:: Form.template_name_label
The template used to render a field's ``<label>``, used when calling
@ -998,16 +990,12 @@ Customizing the error list format
.. attribute:: renderer
.. versionadded:: 4.0
Specifies the :doc:`renderer <renderers>` to use for ``ErrorList``.
Defaults to ``None`` which means to use the default renderer
specified by the :setting:`FORM_RENDERER` setting.
.. attribute:: template_name
.. versionadded:: 4.0
The name of the template used when calling ``__str__`` or
:meth:`render`. By default this is
``'django/forms/errors/list/default.html'`` which is a proxy for the
@ -1015,16 +1003,12 @@ Customizing the error list format
.. attribute:: template_name_text
.. versionadded:: 4.0
The name of the template used when calling :meth:`.as_text`. By default
this is ``'django/forms/errors/list/text.html'``. This template renders
the errors as a list of bullet points.
.. attribute:: template_name_ul
.. versionadded:: 4.0
The name of the template used when calling :meth:`.as_ul`. By default
this is ``'django/forms/errors/list/ul.html'``. This template renders
the errors in ``<li>`` tags with a wrapping ``<ul>`` with the CSS
@ -1032,8 +1016,6 @@ Customizing the error list format
.. method:: get_context()
.. versionadded:: 4.0
Return context for rendering of errors in a template.
The available context is:
@ -1043,8 +1025,6 @@ Customizing the error list format
.. method:: render(template_name=None, context=None, renderer=None)
.. versionadded:: 4.0
The render method is called by ``__str__`` as well as by the
:meth:`.as_ul` method.
@ -1069,10 +1049,6 @@ Customizing the error list format
overriding the default template, see also
:ref:`overriding-built-in-form-templates`.
.. versionchanged:: 4.0
Rendering of :class:`ErrorList` was moved to the template engine.
.. deprecated:: 4.0
The ability to return a ``str`` when calling the ``__str__`` method is
@ -1341,10 +1317,6 @@ Methods of ``BoundField``
overriding the default template, see also
:ref:`overriding-built-in-form-templates`.
.. versionchanged:: 4.0
The label is now rendered using the template engine.
.. versionchanged:: 4.1
The ``tag`` argument was added.

View file

@ -1350,11 +1350,6 @@ generating choices. See :ref:`iterating-relationship-choices` for details.
def label_from_instance(self, obj):
return "My Object #%i" % obj.id
.. versionchanged:: 4.0
Support for containing ``%(value)s`` in the ``invalid_choice`` error
message was added.
``ModelMultipleChoiceField``
----------------------------

View file

@ -16,7 +16,3 @@ Formset API reference. For introductory material about formsets, see the
Returns a ``FormSet`` class for the given ``form`` class.
See :doc:`formsets </topics/forms/formsets>` for example usage.
.. versionchanged:: 4.0
The ``renderer`` argument was added.

View file

@ -72,10 +72,6 @@ Model Form API reference. For introductory material about model forms, see the
See :ref:`model-formsets` for example usage.
.. versionchanged:: 4.0
The ``renderer`` argument was added.
.. versionchanged:: 4.1
The ``edit_only`` argument was added.
@ -94,10 +90,6 @@ Model Form API reference. For introductory material about model forms, see the
See :ref:`inline-formsets` for example usage.
.. versionchanged:: 4.0
The ``renderer`` argument was added.
.. versionchanged:: 4.1
The ``edit_only`` argument was added.

View file

@ -182,8 +182,6 @@ needs can be located.
Context available in formset templates
======================================
.. versionadded:: 4.0
Formset templates receive a context from :meth:`.BaseFormSet.get_context`. By
default, formsets receive a dictionary with the following values:
@ -192,8 +190,6 @@ default, formsets receive a dictionary with the following values:
Context available in form templates
===================================
.. versionadded:: 4.0
Form templates receive a context from :meth:`.Form.get_context`. By default,
forms receive a dictionary with the following values:
@ -224,8 +220,6 @@ defines ``widget['subwidgets']`` for looping purposes.
Overriding built-in formset templates
=====================================
.. versionadded:: 4.0
:attr:`.BaseFormSet.template_name`
To override formset templates, you must use the :class:`TemplatesSetting`
@ -237,8 +231,6 @@ renderer. Then overriding widget templates works :doc:`the same as
Overriding built-in form templates
==================================
.. versionadded:: 4.0
:attr:`.Form.template_name`
To override form templates, you must use the :class:`TemplatesSetting`

View file

@ -725,11 +725,6 @@ that specifies the template used to render each choice. For example, for the
...
</div>
.. versionchanged:: 4.0
So they are announced more concisely by screen readers, radio buttons
were changed to render in ``<div>`` tags.
For more granular control over the generated markup, you can loop over the
radio buttons in the template. Assuming a form ``myform`` with a field
``beatles`` that uses a ``RadioSelect`` as its widget:
@ -836,11 +831,6 @@ that specifies the template used to render each choice. For example, for the
The outer ``<div>`` container receives the ``id`` attribute of the widget,
if defined, or :attr:`BoundField.auto_id` otherwise.
.. versionchanged:: 4.0
So they are announced more concisely by screen readers, checkboxes were
changed to render in ``<div>`` tags.
Like :class:`RadioSelect`, you can loop over the individual checkboxes for the
widget's choices. Unlike :class:`RadioSelect`, the checkboxes won't include the
``required`` HTML attribute if the field is required because browser validation