mirror of
https://github.com/django/django.git
synced 2025-12-15 21:45:20 +00:00
Removed versionadded/changed annotations for 3.1.
This commit is contained in:
parent
8774b1144c
commit
b7dd89ed53
45 changed files with 0 additions and 392 deletions
|
|
@ -16,15 +16,9 @@ You can expect to see this in future releases. For now, you can use the
|
|||
There is also a whole range of async-native Python libraries that you can
|
||||
integrate with.
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
Support for async views was added.
|
||||
|
||||
Async views
|
||||
===========
|
||||
|
||||
.. versionadded:: 3.1
|
||||
|
||||
Any view can be declared async by making the callable part of it return a
|
||||
coroutine - commonly, this is done using ``async def``. For a function-based
|
||||
view, this means declaring the whole view using ``async def``. For a
|
||||
|
|
|
|||
|
|
@ -705,10 +705,6 @@ The following attributes and methods are available on any subclass of
|
|||
Returns an HMAC of the password field. Used for
|
||||
:ref:`session-invalidation-on-password-change`.
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
The hashing algorithm was changed to the SHA-256.
|
||||
|
||||
:class:`~models.AbstractUser` subclasses :class:`~models.AbstractBaseUser`:
|
||||
|
||||
.. class:: models.AbstractUser
|
||||
|
|
|
|||
|
|
@ -429,10 +429,6 @@ from the ``User`` model.
|
|||
hasher. If the password argument is ``None``, an unusable password is
|
||||
returned (one that will never be accepted by :func:`check_password`).
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
The ``password`` parameter must be a string or bytes if not ``None``.
|
||||
|
||||
.. function:: is_password_usable(encoded_password)
|
||||
|
||||
Returns ``False`` if the password is a result of
|
||||
|
|
|
|||
|
|
@ -628,11 +628,6 @@ Additionally, ``cache_page`` automatically sets ``Cache-Control`` and
|
|||
``Expires`` headers in the response which affect :ref:`downstream caches
|
||||
<downstream-caches>`.
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
In older versions, the ``max-age`` directive from the ``Cache-Control``
|
||||
header had precedence over the cache timeout set by ``cache_page``.
|
||||
|
||||
Specifying per-view cache in the URLconf
|
||||
----------------------------------------
|
||||
|
||||
|
|
@ -930,10 +925,6 @@ particular object::
|
|||
``delete()`` returns ``True`` if the key was successfully deleted, ``False``
|
||||
otherwise.
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
The boolean return value was added.
|
||||
|
||||
.. method:: cache.delete_many(keys, version=None)
|
||||
|
||||
If you want to clear a bunch of keys at once, ``delete_many()`` can take a list
|
||||
|
|
|
|||
|
|
@ -665,10 +665,6 @@ The ``F()`` objects support bitwise operations by ``.bitand()``, ``.bitor()``,
|
|||
|
||||
Oracle doesn't support bitwise XOR operation.
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
Support for ``.bitxor()`` was added.
|
||||
|
||||
.. _using-transforms-in-expressions:
|
||||
|
||||
Expressions can reference transforms
|
||||
|
|
|
|||
|
|
@ -529,10 +529,6 @@ To specify this backend, put the following in your settings::
|
|||
This backend is not intended for use in production -- it is provided as a
|
||||
convenience that can be used during development.
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
Support for :class:`pathlib.Path` was added.
|
||||
|
||||
.. _topic-email-memory-backend:
|
||||
|
||||
In-memory backend
|
||||
|
|
|
|||
|
|
@ -206,8 +206,6 @@ you can pass them in as the ``storage`` argument to a
|
|||
Using a callable
|
||||
----------------
|
||||
|
||||
.. versionadded:: 3.1
|
||||
|
||||
You can use a callable as the :attr:`~django.db.models.FileField.storage`
|
||||
parameter for :class:`~django.db.models.FileField` or
|
||||
:class:`~django.db.models.ImageField`. This allows you to modify the used
|
||||
|
|
|
|||
|
|
@ -291,8 +291,6 @@ object with a :attr:`~django.http.HttpResponse.status_code` of 404.
|
|||
Asynchronous support
|
||||
====================
|
||||
|
||||
.. versionadded:: 3.1
|
||||
|
||||
Middleware can support any combination of synchronous and asynchronous
|
||||
requests. Django will adapt requests to fit the middleware's requirements if it
|
||||
cannot support both, but at a performance penalty.
|
||||
|
|
@ -423,7 +421,3 @@ These are the behavioral differences between using :setting:`MIDDLEWARE` and
|
|||
HTTP response, and then the next middleware in line will see that
|
||||
response. Middleware are never skipped due to a middleware raising an
|
||||
exception.
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
Support for asynchronous requests was added to the ``MiddlewareMixin``.
|
||||
|
|
|
|||
|
|
@ -157,10 +157,6 @@ A converter is a class that includes the following:
|
|||
and as a consequence :func:`~django.urls.reverse` will raise
|
||||
:class:`~django.urls.NoReverseMatch` unless another URL pattern matches.
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
Support for raising ``ValueError`` to indicate no match was added.
|
||||
|
||||
For example::
|
||||
|
||||
class FourDigitYearConverter:
|
||||
|
|
|
|||
|
|
@ -208,8 +208,6 @@ in a test view. For example::
|
|||
Async views
|
||||
===========
|
||||
|
||||
.. versionadded:: 3.1
|
||||
|
||||
As well as being synchronous functions, views can also be asynchronous
|
||||
("async") functions, normally defined using Python's ``async def`` syntax.
|
||||
Django will automatically detect these and run them in an async context.
|
||||
|
|
|
|||
|
|
@ -272,10 +272,6 @@ In a case like this, consider something like the following::
|
|||
|
||||
a format specification for argument 'name', as in 'msgstr[0]', doesn't exist in 'msgid'
|
||||
|
||||
.. versionchanged: 2.2.12
|
||||
|
||||
Added support for different plural equations in ``.po`` files.
|
||||
|
||||
.. _contextual-markers:
|
||||
|
||||
Contextual markers
|
||||
|
|
@ -626,11 +622,6 @@ using the ``context`` keyword:
|
|||
|
||||
{% translate "May" context "month name" %}
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
The ``trans`` tag was renamed to ``translate``. The ``trans``
|
||||
tag is still supported as an alias for backwards compatibility.
|
||||
|
||||
.. templatetag:: blocktrans
|
||||
.. templatetag:: blocktranslate
|
||||
|
||||
|
|
@ -749,11 +740,6 @@ will result in the entry ``"First sentence. Second paragraph."`` in the PO file,
|
|||
compared to ``"\n First sentence.\n Second paragraph.\n"``, if the
|
||||
``trimmed`` option had not been specified.
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
The ``blocktrans`` tag was renamed to ``blocktranslate``. The ``blocktrans``
|
||||
tag is still supported as an alias for backwards compatibility.
|
||||
|
||||
String literals passed to tags and filters
|
||||
------------------------------------------
|
||||
|
||||
|
|
@ -1817,12 +1803,6 @@ set, to ``/``, depending on the nature of the request:
|
|||
the ``next`` parameter was set. Otherwise a 204 status code (No Content) will
|
||||
be returned.
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
In older versions, the distinction for the fallback is based on whether the
|
||||
``X-Requested-With`` header is set to the value ``XMLHttpRequest``. This is
|
||||
set by the jQuery ``ajax()`` method.
|
||||
|
||||
Here's example HTML template code:
|
||||
|
||||
.. code-block:: html+django
|
||||
|
|
|
|||
|
|
@ -277,11 +277,6 @@ function::
|
|||
Also note that GeoDjango provides a :doc:`customized GeoJSON serializer
|
||||
</ref/contrib/gis/serializers>`.
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
All data is now dumped with Unicode. If you need the previous behavior,
|
||||
pass ``ensure_ascii=True`` to the ``serializers.serialize()`` function.
|
||||
|
||||
``DjangoJSONEncoder``
|
||||
~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
|
|
@ -341,11 +336,6 @@ again a mapping with the key being name of the field and the value the value::
|
|||
|
||||
Referential fields are again represented by the PK or sequence of PKs.
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
All data is now dumped with Unicode. If you need the previous behavior,
|
||||
pass ``allow_unicode=False`` to the ``serializers.serialize()`` function.
|
||||
|
||||
.. _topics-serialization-natural-keys:
|
||||
|
||||
Natural keys
|
||||
|
|
|
|||
|
|
@ -101,10 +101,6 @@ generate signatures. You can use a different secret by passing it to the
|
|||
and underscores. ``algorithm`` must be an algorithm supported by
|
||||
:py:mod:`hashlib`, it defaults to ``'sha256'``.
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
The ``algorithm`` parameter was added.
|
||||
|
||||
.. versionchanged:: 3.2
|
||||
|
||||
The ``sign_object()`` and ``unsign_object()`` methods were added.
|
||||
|
|
@ -197,10 +193,6 @@ created within a specified period of time::
|
|||
otherwise raises ``SignatureExpired``. The ``max_age`` parameter can
|
||||
accept an integer or a :py:class:`datetime.timedelta` object.
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
The ``algorithm`` parameter was added.
|
||||
|
||||
.. _signing-complex-data:
|
||||
|
||||
Protecting complex data structures
|
||||
|
|
|
|||
|
|
@ -573,10 +573,6 @@ execute and tear down the test suite.
|
|||
custom arguments by calling ``parser.add_argument()`` inside the method, so
|
||||
that the :djadmin:`test` command will be able to use those arguments.
|
||||
|
||||
.. versionadded:: 3.1
|
||||
|
||||
The ``buffer`` argument was added.
|
||||
|
||||
.. versionadded:: 3.2
|
||||
|
||||
The ``enable_faulthandler`` and ``timing`` arguments were added.
|
||||
|
|
@ -671,10 +667,6 @@ Methods
|
|||
|
||||
Runs the :doc:`system checks </topics/checks>` on the test ``databases``.
|
||||
|
||||
.. versionadded:: 3.1
|
||||
|
||||
The ``databases`` parameter was added.
|
||||
|
||||
.. method:: DiscoverRunner.run_suite(suite, **kwargs)
|
||||
|
||||
Runs the test suite.
|
||||
|
|
|
|||
|
|
@ -769,11 +769,6 @@ If your tests make any database queries, use subclasses
|
|||
:exc:`unittest.SkipTest` in ``setUpClass()``, be sure to do it before
|
||||
calling ``super()`` to avoid this.
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
||||
The ``debug()`` method was implemented to allow running a test without
|
||||
collecting the result and catching exceptions.
|
||||
|
||||
``TransactionTestCase``
|
||||
-----------------------
|
||||
|
||||
|
|
@ -1806,8 +1801,6 @@ won't be run.
|
|||
Testing asynchronous code
|
||||
=========================
|
||||
|
||||
.. versionadded:: 3.1
|
||||
|
||||
If you merely want to test the output of your asynchronous views, the standard
|
||||
test client will run them inside their own asynchronous loop without any extra
|
||||
work needed on your part.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue