Removed versionadded/changed annotations for 1.10.

16 files changed, 0 insertions, 131 deletions

diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt
index 40675d2ef6..0f750adc2b 100644
--- a/docs/topics/auth/customizing.txt
+++ b/docs/topics/auth/customizing.txt
@@ -260,11 +260,6 @@ authenticated users do not.
 Do not forget to test for the ``is_active`` attribute of the user in your own
 backend permission methods.
 
-.. versionchanged:: 1.10
-
-    In older versions, the :class:`~django.contrib.auth.backends.ModelBackend`
-    allowed inactive users to authenticate.
-
 Handling object permissions
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -661,8 +656,6 @@ The following attributes and methods are available on any subclass of
 
     .. method:: clean()
 
-        .. versionadded:: 1.10
-
         Normalizes the username by calling :meth:`normalize_username`. If you
         override this method, be sure to call ``super()`` to retain the
         normalization.
@@ -677,8 +670,6 @@ The following attributes and methods are available on any subclass of
 
     .. classmethod:: normalize_username(username)
 
-        .. versionadded:: 1.10
-
         Applies NFKC Unicode normalization to usernames so that visually
         identical characters with different Unicode code points are considered
         identical.
diff --git a/docs/topics/auth/default.txt b/docs/topics/auth/default.txt
index b1f111c092..7aea283a10 100644
--- a/docs/topics/auth/default.txt
+++ b/docs/topics/auth/default.txt
@@ -358,14 +358,6 @@ If you have an authenticated user you want to attach to the current session
                 # Return an 'invalid login' error message.
                 ...
 
-    .. versionchanged:: 1.10
-
-        In older versions, when you're manually logging a user in, you *must*
-        successfully authenticate the user with
-        :func:`~django.contrib.auth.authenticate()` before you call
-        :func:`~django.contrib.auth.login()`. Now you can set the backend using
-        the new ``backend`` argument.
-
 Selecting the authentication backend
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -956,10 +948,6 @@ implementation details see :ref:`using-the-views`.
     The optional arguments of this view are similar to the class-based
     ``LoginView`` attributes.
 
-    .. versionadded:: 1.10
-
-        The ``redirect_authenticated_user`` parameter was added.
-
 .. class:: LoginView
 
     .. versionadded:: 1.11
diff --git a/docs/topics/auth/passwords.txt b/docs/topics/auth/passwords.txt
index 7015e65404..128a2906cb 100644
--- a/docs/topics/auth/passwords.txt
+++ b/docs/topics/auth/passwords.txt
@@ -76,8 +76,6 @@ to modify this setting.
 Using Argon2 with Django
 ------------------------
 
-.. versionadded:: 1.10
-
 Argon2_ is the winner of the 2015 `Password Hashing Competition`_, a community
 organized open competition to select a next generation hashing algorithm. It's
 designed not to be easier to compute on custom hardware than it is to compute
diff --git a/docs/topics/checks.txt b/docs/topics/checks.txt
index 355e85714e..59ead9d5a7 100644
--- a/docs/topics/checks.txt
+++ b/docs/topics/checks.txt
@@ -133,10 +133,6 @@ perform any extra checks you need, and append any messages to those generated
 by the base class. It's recommended that you delegate each check to separate
 methods.
 
-.. versionchanged:: 1.10
-
-    Database backend checks were added.
-
 Consider an example where you are implementing a custom field named
 ``RangedIntegerField``. This field adds ``min`` and ``max`` arguments to the
 constructor of ``IntegerField``. You may want to add a check to ensure that users
diff --git a/docs/topics/db/managers.txt b/docs/topics/db/managers.txt
index 2867db02d9..a8923e2e36 100644
--- a/docs/topics/db/managers.txt
+++ b/docs/topics/db/managers.txt
@@ -367,13 +367,6 @@ Here's how Django handles custom managers and :ref:`model inheritance
    <django.db.models.Options.default_manager_name>`, or the first manager
    declared on the model, or the default manager of the first parent model.
 
-.. versionchanged:: 1.10
-
-    In older versions, manager inheritance varied depending on the type of
-    model inheritance (i.e. :ref:`abstract-base-classes`,
-    :ref:`multi-table-inheritance`, or :ref:`proxy-models`), especially
-    with regards to electing the default manager.
-
 These rules provide the necessary flexibility if you want to install a
 collection of custom managers on a group of models, via an abstract base
 class, but still customize the default manager. For example, suppose you have
diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt
index 07caa00b02..1ce164f532 100644
--- a/docs/topics/db/models.txt
+++ b/docs/topics/db/models.txt
@@ -1034,11 +1034,6 @@ attribute was omitted, the reverse name for the ``m2m`` field would be
 ``childa_set`` in the ``ChildA`` case and ``childb_set`` for the ``ChildB``
 field.
 
-.. versionchanged:: 1.10
-
-   Interpolation of  ``'%(app_label)s'`` and ``'%(class)s'`` for
-   ``related_query_name`` was added.
-
 .. _multi-table-inheritance:
 
 Multi-table inheritance
@@ -1236,11 +1231,6 @@ proxy model can inherit from any number of abstract model classes, providing
 they do *not* define any model fields. A proxy model may also inherit from any
 number of proxy models that share a common non-abstract parent class.
 
-.. versionchanged:: 1.10
-
-    In earlier versions, a proxy model couldn't inherit more than one proxy
-    model that shared the same parent class.
-
 Proxy model managers
 ~~~~~~~~~~~~~~~~~~~~
 
@@ -1374,10 +1364,6 @@ This restriction doesn't apply to model fields inherited from an abstract
 model. Such fields may be overridden with another field or value, or be removed
 by setting ``field_name = None``.
 
-.. versionchanged:: 1.10
-
-    The ability to override abstract fields was added.
-
 .. warning::
 
     Model managers are inherited from abstract base classes. Overriding an
diff --git a/docs/topics/db/multi-db.txt b/docs/topics/db/multi-db.txt
index 83ac9b7c5e..69885453b3 100644
--- a/docs/topics/db/multi-db.txt
+++ b/docs/topics/db/multi-db.txt
@@ -109,11 +109,6 @@ creating new migrations. By default, it checks only the ``default`` database,
 but it consults the :meth:`allow_migrate` method of :ref:`routers
 <topics-db-multi-db-routing>` if any are installed.
 
-.. versionchanged:: 1.10
-
-    Migration consistency checks were added. Checks based on database routers
-    were added in 1.10.1.
-
 .. _topics-db-multi-db-routing:
 
 Automatic database routing
diff --git a/docs/topics/forms/media.txt b/docs/topics/forms/media.txt
index adbd2c377e..0bdf237a21 100644
--- a/docs/topics/forms/media.txt
+++ b/docs/topics/forms/media.txt
@@ -249,10 +249,6 @@ Or if :mod:`~django.contrib.staticfiles` is configured using the
     <script type="text/javascript" src="https://static.example.com/animations.27e20196a850.js"></script>
     <script type="text/javascript" src="http://othersite.com/actions.js"></script>
 
-.. versionchanged:: 1.10
-
-    Older versions didn't serve assets using :mod:`django.contrib.staticfiles`.
-
 ``Media`` objects
 =================
 
diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt
index eb397a3d4a..b0115cef7e 100644
--- a/docs/topics/forms/modelforms.txt
+++ b/docs/topics/forms/modelforms.txt
@@ -342,16 +342,6 @@ there is one, for that field. This behavior doesn't apply to fields that use
 form submission. Use a custom form field or widget if you're designing an API
 and want the default fallback for a :class:`~django.db.models.BooleanField`.
 
-.. versionchanged:: 1.10.1
-
-    Older versions don't have the exception for
-    :class:`~django.forms.CheckboxInput` which means that unchecked checkboxes
-    receive a value of ``True`` if that's the model field default.
-
-.. versionchanged:: 1.10.2
-
-    The :meth:`~django.forms.Widget.value_omitted_from_data` method was added.
-
 This ``save()`` method accepts an optional ``commit`` keyword argument, which
 accepts either ``True`` or ``False``. If you call ``save()`` with
 ``commit=False``, then it will return an object that hasn't yet been saved to
diff --git a/docs/topics/http/middleware.txt b/docs/topics/http/middleware.txt
index d5e8927065..09cf78557d 100644
--- a/docs/topics/http/middleware.txt
+++ b/docs/topics/http/middleware.txt
@@ -86,15 +86,6 @@ caveats:
 * Unlike the ``__call__()`` method which is called once per request,
   ``__init__()`` is called only *once*, when the Web server starts.
 
-.. versionchanged:: 1.10
-
-    In older versions, ``__init__()`` wasn't called until the Web server
-    responded to its first request.
-
-    In older versions, ``__init__()`` didn't accept any arguments. To allow
-    your middleware to be used in Django 1.9 and earlier, make ``get_response``
-    an optional argument (``get_response=None``).
-
 Marking middleware as unused
 ----------------------------
 
diff --git a/docs/topics/i18n/translation.txt b/docs/topics/i18n/translation.txt
index 4605f998e5..bb3796a32e 100644
--- a/docs/topics/i18n/translation.txt
+++ b/docs/topics/i18n/translation.txt
@@ -988,8 +988,6 @@ The ``JavaScriptCatalog`` view
 
 .. module:: django.views.i18n
 
-.. versionadded:: 1.10
-
 .. class:: JavaScriptCatalog
 
     A view that produces a JavaScript code library with functions that mimic
@@ -1216,8 +1214,6 @@ will render a conditional expression. This will evaluate to either a ``true``
 The ``JSONCatalog`` view
 ------------------------
 
-.. versionadded:: 1.10
-
 .. class:: JSONCatalog
 
     In order to use another client-side library to handle translations, you may
@@ -1379,22 +1375,12 @@ will be::
     >>> reverse('news:index')
     '/nl/news/'
 
-.. versionadded:: 1.10
-
-    The ``prefix_default_language`` parameter was added.
-
 .. warning::
 
     :func:`~django.conf.urls.i18n.i18n_patterns` is only allowed in a root
     URLconf. Using it within an included URLconf will throw an
     :exc:`~django.core.exceptions.ImproperlyConfigured` exception.
 
-.. versionchanged:: 1.10
-
-    In older version, using ``i18n_patterns`` in a root URLconf different from
-    :setting:`ROOT_URLCONF` by setting :attr:`request.urlconf
-    <django.http.HttpRequest.urlconf>` wasn't supported.
-
 .. warning::
 
     Ensure that you don't have non-prefixed URL patterns that might collide
@@ -1814,11 +1800,6 @@ set, to ``/``, depending on the nature of the request:
   parameter was set. Otherwise a 204 status code (No Content) will be returned.
 * For non-AJAX requests, the fallback will always be performed.
 
-.. versionchanged:: 1.10
-
-    Returning a 204 status code for AJAX requests when no redirect is specified
-    is new.
-
 Here's example HTML template code:
 
 .. code-block:: html+django
diff --git a/docs/topics/logging.txt b/docs/topics/logging.txt
index 15a49f0d4d..859f18516d 100644
--- a/docs/topics/logging.txt
+++ b/docs/topics/logging.txt
@@ -481,8 +481,6 @@ Messages to this logger have the following extra context:
 ``django.server``
 ~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 1.10
-
 Log messages related to the handling of requests received by the server invoked
 by the :djadmin:`runserver` command. HTTP 5XX responses are logged as ``ERROR``
 messages, 4XX responses are logged as ``WARNING`` messages, and everything else
@@ -584,10 +582,6 @@ Messages to this logger have ``params`` and ``sql`` in their extra context (but
 unlike ``django.db.backends``, not duration). The values have the same meaning
 as explained in :ref:`django-db-logger`.
 
-.. versionadded:: 1.10
-
-    The ``extra`` context was added.
-
 Handlers
 --------
 
diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index 2be05903ae..e8675fe545 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -314,11 +314,6 @@ new migrations until it's fixed. When using multiple databases, you can use the
 <topics-db-multi-db-routing>` to control which databases
 :djadmin:`makemigrations` checks for consistent history.
 
-.. versionchanged:: 1.10
-
-    Migration consistency checks were added. Checks based on database routers
-    were added in 1.10.1.
-
 Adding migrations to apps
 =========================
 
@@ -679,10 +674,6 @@ Django can serialize the following:
 - Any class reference (must be in module's top-level scope)
 - Anything with a custom ``deconstruct()`` method (:ref:`see below <custom-deconstruct-method>`)
 
-.. versionchanged:: 1.10
-
-    Serialization support for ``enum.Enum`` was added.
-
 .. versionchanged:: 1.11
 
     Serialization support for ``uuid.UUID`` was added.
diff --git a/docs/topics/serialization.txt b/docs/topics/serialization.txt
index 5db5e656ec..9f7a4f41c6 100644
--- a/docs/topics/serialization.txt
+++ b/docs/topics/serialization.txt
@@ -305,10 +305,6 @@ The JSON serializer uses ``DjangoJSONEncoder`` for encoding. A subclass of
 :class:`~decimal.Decimal`, ``Promise`` (``django.utils.functional.lazy()`` objects), :class:`~uuid.UUID`
    A string representation of the object.
 
-.. versionchanged:: 1.10
-
-    Support for ``Promise`` was added.
-
 .. versionchanged:: 1.11
 
     Support for :class:`~datetime.timedelta` was added.
diff --git a/docs/topics/templates.txt b/docs/topics/templates.txt
index 3ee9a01efd..a819acf3f0 100644
--- a/docs/topics/templates.txt
+++ b/docs/topics/templates.txt
@@ -308,10 +308,6 @@ applications. This generic name was kept for backwards-compatibility.
 
       Only set it to ``False`` if you're rendering non-HTML templates!
 
-  .. versionadded:: 1.10
-
-      The ``autoescape`` option was added.
-
 * ``'context_processors'``: a list of dotted Python paths to callables that
   are used to populate the context when a template is rendered with a request.
   These callables take a request object as their argument and return a
diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt
index 5bb34be1a3..b8c799619e 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -371,12 +371,6 @@ Use the ``django.test.Client`` class to make requests.
         :meth:`~django.contrib.auth.models.UserManager.create_user` helper
         method to create a new user with a correctly hashed password.
 
-        .. versionchanged:: 1.10
-
-            In previous versions, inactive users (:attr:`is_active=False
-            <django.contrib.auth.models.User.is_active>`) were not permitted
-            to login.
-
     .. method:: Client.force_login(user, backend=None)
 
         If your site uses Django's :doc:`authentication
@@ -795,11 +789,6 @@ The class:
 
 * Checks deferrable database constraints at the end of each test.
 
-.. versionchanged:: 1.10
-
-    The check for deferrable database constraints at the end of each test was
-    added.
-
 It also provides an additional method:
 
 .. classmethod:: TestCase.setUpTestData()
@@ -1604,8 +1593,6 @@ your test suite.
 Tagging tests
 -------------
 
-.. versionadded:: 1.10
-
 You can tag your tests so you can easily run a particular subset. For example,
 you might label fast or slow tests::