mirror of
https://github.com/django/django.git
synced 2025-08-19 02:01:29 +00:00
Removed versionadded/changed annotations for 5.0.
This also removes remaining versionadded/changed annotations for older versions.
This commit is contained in:
parent
ec44247f59
commit
05cce083ad
44 changed files with 0 additions and 379 deletions
|
@ -33,26 +33,14 @@ a :class:`django.http.HttpResponseNotAllowed` if the conditions are not met.
|
|||
|
||||
Note that request methods should be in uppercase.
|
||||
|
||||
.. versionchanged:: 5.0
|
||||
|
||||
Support for wrapping asynchronous view functions was added.
|
||||
|
||||
.. function:: require_GET()
|
||||
|
||||
Decorator to require that a view only accepts the GET method.
|
||||
|
||||
.. versionchanged:: 5.0
|
||||
|
||||
Support for wrapping asynchronous view functions was added.
|
||||
|
||||
.. function:: require_POST()
|
||||
|
||||
Decorator to require that a view only accepts the POST method.
|
||||
|
||||
.. versionchanged:: 5.0
|
||||
|
||||
Support for wrapping asynchronous view functions was added.
|
||||
|
||||
.. function:: require_safe()
|
||||
|
||||
Decorator to require that a view only accepts the GET and HEAD methods.
|
||||
|
@ -67,10 +55,6 @@ a :class:`django.http.HttpResponseNotAllowed` if the conditions are not met.
|
|||
such as link checkers, rely on HEAD requests, you might prefer
|
||||
using ``require_safe`` instead of ``require_GET``.
|
||||
|
||||
.. versionchanged:: 5.0
|
||||
|
||||
Support for wrapping asynchronous view functions was added.
|
||||
|
||||
Conditional view processing
|
||||
===========================
|
||||
|
||||
|
@ -87,10 +71,6 @@ control caching behavior on particular views.
|
|||
headers; see
|
||||
:doc:`conditional view processing </topics/conditional-view-processing>`.
|
||||
|
||||
.. versionchanged:: 5.0
|
||||
|
||||
Support for wrapping asynchronous view functions was added.
|
||||
|
||||
.. module:: django.views.decorators.gzip
|
||||
|
||||
GZip compression
|
||||
|
@ -105,10 +85,6 @@ compression on a per-view basis.
|
|||
It sets the ``Vary`` header accordingly, so that caches will base their
|
||||
storage on the ``Accept-Encoding`` header.
|
||||
|
||||
.. versionchanged:: 5.0
|
||||
|
||||
Support for wrapping asynchronous view functions was added.
|
||||
|
||||
.. module:: django.views.decorators.vary
|
||||
|
||||
Vary headers
|
||||
|
@ -119,10 +95,6 @@ caching based on specific request headers.
|
|||
|
||||
.. function:: vary_on_cookie(func)
|
||||
|
||||
.. versionchanged:: 5.0
|
||||
|
||||
Support for wrapping asynchronous view functions was added.
|
||||
|
||||
.. function:: vary_on_headers(*headers)
|
||||
|
||||
The ``Vary`` header defines which request headers a cache mechanism should take
|
||||
|
@ -130,10 +102,6 @@ caching based on specific request headers.
|
|||
|
||||
See :ref:`using vary headers <using-vary-headers>`.
|
||||
|
||||
.. versionchanged:: 5.0
|
||||
|
||||
Support for wrapping asynchronous view functions was added.
|
||||
|
||||
.. module:: django.views.decorators.cache
|
||||
|
||||
Caching
|
||||
|
@ -149,10 +117,6 @@ client-side caching.
|
|||
:func:`~django.utils.cache.patch_cache_control` for the details of the
|
||||
transformation.
|
||||
|
||||
.. versionchanged:: 5.0
|
||||
|
||||
Support for wrapping asynchronous view functions was added.
|
||||
|
||||
.. function:: never_cache(view_func)
|
||||
|
||||
This decorator adds an ``Expires`` header to the current date/time.
|
||||
|
@ -163,10 +127,6 @@ client-side caching.
|
|||
|
||||
Each header is only added if it isn't already set.
|
||||
|
||||
.. versionchanged:: 5.0
|
||||
|
||||
Support for wrapping asynchronous view functions was added.
|
||||
|
||||
.. module:: django.views.decorators.common
|
||||
|
||||
Common
|
||||
|
@ -180,6 +140,3 @@ customization of :class:`~django.middleware.common.CommonMiddleware` behavior.
|
|||
This decorator allows individual views to be excluded from
|
||||
:setting:`APPEND_SLASH` URL normalization.
|
||||
|
||||
.. versionchanged:: 5.0
|
||||
|
||||
Support for wrapping asynchronous view functions was added.
|
||||
|
|
|
@ -239,10 +239,6 @@ Note: As with ``get()``, a
|
|||
:class:`~django.core.exceptions.MultipleObjectsReturned` exception
|
||||
will be raised if more than one object is found.
|
||||
|
||||
.. versionchanged:: 5.0
|
||||
|
||||
``aget_object_or_404()`` function was added.
|
||||
|
||||
``get_list_or_404()``
|
||||
=====================
|
||||
|
||||
|
@ -291,6 +287,3 @@ This example is equivalent to::
|
|||
if not my_objects:
|
||||
raise Http404("No MyModel matches the given query.")
|
||||
|
||||
.. versionchanged:: 5.0
|
||||
|
||||
``aget_list_or_404()`` function was added.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue