mirror of
https://github.com/django/django.git
synced 2025-11-19 11:15:44 +00:00
Removed versionadded/changed annotations for 5.2.
This commit is contained in:
parent
1db79d8acf
commit
00a84fc6f3
38 changed files with 0 additions and 310 deletions
|
|
@ -802,10 +802,6 @@ utility methods:
|
|||
Retrieves a user instance using the contents of the field
|
||||
nominated by ``USERNAME_FIELD``.
|
||||
|
||||
.. versionchanged:: 5.2
|
||||
|
||||
``aget_by_natural_key()`` method was added.
|
||||
|
||||
Extending Django's default ``User``
|
||||
-----------------------------------
|
||||
|
||||
|
|
@ -1205,8 +1201,6 @@ using the :setting:`AUTH_USER_MODEL` setting in your ``settings.py``::
|
|||
Adding an async interface
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. versionadded:: 5.2
|
||||
|
||||
To optimize performance when called from an async context authentication,
|
||||
backends can implement async versions of each function - ``aget_user(user_id)``
|
||||
and ``aauthenticate(request, **credentials)``. When an authentication backend
|
||||
|
|
|
|||
|
|
@ -604,8 +604,6 @@ Django includes four validators:
|
|||
|
||||
.. method:: get_error_message()
|
||||
|
||||
.. versionadded:: 5.2
|
||||
|
||||
A hook for customizing the ``ValidationError`` error message. Defaults
|
||||
to ``"This password is too short. It must contain at least <min_length>
|
||||
characters."``.
|
||||
|
|
@ -634,8 +632,6 @@ Django includes four validators:
|
|||
|
||||
.. method:: get_error_message()
|
||||
|
||||
.. versionadded:: 5.2
|
||||
|
||||
A hook for customizing the ``ValidationError`` error message. Defaults
|
||||
to ``"The password is too similar to the <user_attribute>."``.
|
||||
|
||||
|
|
@ -657,8 +653,6 @@ Django includes four validators:
|
|||
|
||||
.. method:: get_error_message()
|
||||
|
||||
.. versionadded:: 5.2
|
||||
|
||||
A hook for customizing the ``ValidationError`` error message. Defaults
|
||||
to ``"This password is too common."``.
|
||||
|
||||
|
|
@ -673,8 +667,6 @@ Django includes four validators:
|
|||
|
||||
.. method:: get_error_message()
|
||||
|
||||
.. versionadded:: 5.2
|
||||
|
||||
A hook for customizing the ``ValidationError`` error message. Defaults
|
||||
to ``"This password is entirely numeric."``.
|
||||
|
||||
|
|
|
|||
|
|
@ -324,7 +324,3 @@ preference, use :func:`django.http.HttpRequest.get_preferred_type`::
|
|||
"pk": self.object.pk,
|
||||
}
|
||||
return JsonResponse(data)
|
||||
|
||||
.. versionchanged:: 5.2
|
||||
|
||||
The :meth:`.HttpRequest.get_preferred_type` method was added.
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
Composite primary keys
|
||||
======================
|
||||
|
||||
.. versionadded:: 5.2
|
||||
|
||||
In Django, each model has a primary key. By default, this primary key consists
|
||||
of a single field.
|
||||
|
||||
|
|
|
|||
|
|
@ -350,11 +350,6 @@ email backend API :ref:`provides an alternative
|
|||
:class:`EmailAttachment`, or a tuple with attributes
|
||||
``(filename, content, mimetype)``.
|
||||
|
||||
.. versionchanged:: 5.2
|
||||
|
||||
Support for :class:`EmailAttachment` items of ``attachments`` was
|
||||
added.
|
||||
|
||||
.. versionchanged:: 6.0
|
||||
|
||||
Support for :class:`~email.message.MIMEPart` objects in the
|
||||
|
|
@ -515,8 +510,6 @@ email backend API :ref:`provides an alternative
|
|||
|
||||
.. class:: EmailAttachment
|
||||
|
||||
.. versionadded:: 5.2
|
||||
|
||||
A named tuple to store attachments to an email.
|
||||
|
||||
The named tuple has the following indexes:
|
||||
|
|
@ -555,11 +548,6 @@ Django's email library, you can do this using the
|
|||
Alternatives should only be added using the :meth:`attach_alternative`
|
||||
method, or passed to the constructor.
|
||||
|
||||
.. versionchanged:: 5.2
|
||||
|
||||
In older versions, ``alternatives`` was a list of regular tuples,
|
||||
as opposed to :class:`EmailAlternative` named tuples.
|
||||
|
||||
.. method:: attach_alternative(content, mimetype)
|
||||
|
||||
Attach an alternative representation of the message body in the email.
|
||||
|
|
@ -579,8 +567,6 @@ Django's email library, you can do this using the
|
|||
|
||||
.. method:: body_contains(text)
|
||||
|
||||
.. versionadded:: 5.2
|
||||
|
||||
Returns a boolean indicating whether the provided ``text`` is
|
||||
contained in the email ``body`` and in all attached MIME type
|
||||
``text/*`` alternatives.
|
||||
|
|
@ -599,8 +585,6 @@ Django's email library, you can do this using the
|
|||
|
||||
.. class:: EmailAlternative
|
||||
|
||||
.. versionadded:: 5.2
|
||||
|
||||
A named tuple to store alternative versions of email content.
|
||||
|
||||
The named tuple has the following indexes:
|
||||
|
|
|
|||
|
|
@ -136,8 +136,6 @@ paths to these files.
|
|||
``Script`` objects
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. versionadded:: 5.2
|
||||
|
||||
.. class:: Script(src, **attributes)
|
||||
|
||||
Represents a script file.
|
||||
|
|
@ -321,10 +319,6 @@ HTML:
|
|||
async>
|
||||
</script>
|
||||
|
||||
.. versionchanged:: 5.2
|
||||
|
||||
The object class ``Script`` was added.
|
||||
|
||||
``Media`` objects
|
||||
=================
|
||||
|
||||
|
|
|
|||
|
|
@ -125,10 +125,6 @@ This example is equivalent to::
|
|||
``True`` ``True`` 308
|
||||
========= ================ ================
|
||||
|
||||
.. versionchanged:: 5.2
|
||||
|
||||
The argument ``preserve_request`` was added.
|
||||
|
||||
Examples
|
||||
--------
|
||||
|
||||
|
|
|
|||
|
|
@ -423,11 +423,6 @@ Then add the module containing the serializer definitions to your
|
|||
"json": "django.core.serializers.json",
|
||||
}
|
||||
|
||||
.. versionchanged:: 5.2
|
||||
|
||||
A ``Deserializer`` class definition was added to each of the provided
|
||||
serialization formats.
|
||||
|
||||
.. _topics-serialization-natural-keys:
|
||||
|
||||
Natural keys
|
||||
|
|
|
|||
|
|
@ -281,11 +281,6 @@ To prevent serialized data from being loaded twice, setting
|
|||
:data:`~django.db.models.signals.post_migrate` signal when flushing the test
|
||||
database.
|
||||
|
||||
.. versionchanged:: 5.2
|
||||
|
||||
For :class:`TransactionTestCase`, serialized migration data is made
|
||||
available during ``setUpClass()``.
|
||||
|
||||
Other test conditions
|
||||
---------------------
|
||||
|
||||
|
|
|
|||
|
|
@ -1254,11 +1254,6 @@ By default, fixtures are only loaded into the ``default`` database. If you are
|
|||
using multiple databases and set :attr:`TransactionTestCase.databases`,
|
||||
fixtures will be loaded into all specified databases.
|
||||
|
||||
.. versionchanged:: 5.2
|
||||
|
||||
For :class:`TransactionTestCase`, fixtures were made available during
|
||||
``setUpClass()``.
|
||||
|
||||
URLconf configuration
|
||||
---------------------
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue