mirror of
https://github.com/django/django.git
synced 2025-08-04 10:59:45 +00:00
Removed versionadded/changed annotations for 2.0.
This commit is contained in:
parent
1cbd3d7874
commit
7543ab1f8d
35 changed files with 0 additions and 234 deletions
|
@ -628,12 +628,6 @@ password resets. You must then provide some key implementation details:
|
|||
first name. If implemented, this replaces the username in the greeting
|
||||
to the user in the header of :mod:`django.contrib.admin`.
|
||||
|
||||
.. versionchanged:: 2.0
|
||||
|
||||
In older versions, subclasses are required to implement
|
||||
``get_short_name()`` and ``get_full_name()`` as ``AbstractBaseUser``
|
||||
has implementations that raise ``NotImplementedError``.
|
||||
|
||||
.. admonition:: Importing ``AbstractBaseUser``
|
||||
|
||||
``AbstractBaseUser`` and ``BaseUserManager`` are importable from
|
||||
|
|
|
@ -659,10 +659,6 @@ example:
|
|||
.. sidebar ..
|
||||
{% endcache %}
|
||||
|
||||
.. versionchanged:: 2.0
|
||||
|
||||
Older versions don't allow a ``None`` timeout.
|
||||
|
||||
Sometimes you might want to cache multiple copies of a fragment depending on
|
||||
some dynamic data that appears inside the fragment. For example, you might want a
|
||||
separate cached copy of the sidebar used in the previous example for every user
|
||||
|
@ -872,10 +868,6 @@ Like ``cache.set()``, ``set_many()`` takes an optional ``timeout`` parameter.
|
|||
On supported backends (memcached), ``set_many()`` returns a list of keys that
|
||||
failed to be inserted.
|
||||
|
||||
.. versionchanged:: 2.0
|
||||
|
||||
The return value containing list of failing keys was added.
|
||||
|
||||
You can delete keys explicitly with ``delete()``. This is an easy way of
|
||||
clearing the cache for a particular object::
|
||||
|
||||
|
|
|
@ -368,10 +368,6 @@ Each ``Author`` in the result set will have the ``num_books`` and
|
|||
rows. The aggregation ``filter`` argument is only useful when using two or
|
||||
more aggregations over the same relations with different conditionals.
|
||||
|
||||
.. versionchanged:: 2.0
|
||||
|
||||
The ``filter`` argument was added to aggregates.
|
||||
|
||||
Order of ``annotate()`` and ``filter()`` clauses
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
|
|
|
@ -2,8 +2,6 @@
|
|||
Database instrumentation
|
||||
========================
|
||||
|
||||
.. versionadded:: 2.0
|
||||
|
||||
To help you understand and control the queries issued by your code, Django
|
||||
provides a hook for installing wrapper functions around the execution of
|
||||
database queries. For example, wrappers can count queries, measure query
|
||||
|
|
|
@ -372,7 +372,3 @@ Calling stored procedures
|
|||
|
||||
with connection.cursor() as cursor:
|
||||
cursor.callproc('test_procedure', [1, 'test'])
|
||||
|
||||
.. versionchanged:: 2.0
|
||||
|
||||
The ``kparams`` argument was added.
|
||||
|
|
|
@ -335,12 +335,6 @@ For example::
|
|||
Combining ``Media`` objects with assets in a conflicting order results in a
|
||||
``MediaOrderConflictWarning``.
|
||||
|
||||
.. versionchanged:: 2.0
|
||||
|
||||
In older versions, the assets of ``Media`` objects are concatenated rather
|
||||
than merged in a way that tries to preserve the relative ordering of the
|
||||
elements in each list.
|
||||
|
||||
``Media`` on Forms
|
||||
==================
|
||||
|
||||
|
|
|
@ -176,8 +176,6 @@ Methods
|
|||
|
||||
.. method:: Paginator.get_page(number)
|
||||
|
||||
.. versionadded:: 2.0
|
||||
|
||||
Returns a :class:`Page` object with the given 1-based index, while also
|
||||
handling out of range and invalid page numbers.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue