Removed obsolete deprecation notes.

1 files changed, 0 insertions, 97 deletions

diff --git a/docs/internals/deprecation.txt b/docs/internals/deprecation.txt
index dd2548b956..6257451e28 100644
--- a/docs/internals/deprecation.txt
+++ b/docs/internals/deprecation.txt
@@ -7,103 +7,6 @@ in a backward incompatible way, following their deprecation, as per the
 :ref:`deprecation policy <internal-release-deprecation-policy>`. More details
 about each item can often be found in the release notes of two versions prior.
 
-1.4
----
-
-See the :doc:`Django 1.2 release notes</releases/1.2>` for more details on
-these changes.
-
-* ``CsrfResponseMiddleware`` and ``CsrfMiddleware`` will be removed.  Use
-  the ``{% csrf_token %}`` template tag inside forms to enable CSRF
-  protection. ``CsrfViewMiddleware`` remains and is enabled by default.
-
-* The old imports for CSRF functionality (``django.contrib.csrf.*``),
-  which moved to core in 1.2, will be removed.
-
-* The ``django.contrib.gis.db.backend`` module will be removed in favor
-  of the specific backends.
-
-* ``SMTPConnection`` will be removed in favor of a generic Email backend API.
-
-* The many to many SQL generation functions on the database backends
-  will be removed.
-
-* The ability to use the ``DATABASE_*`` family of top-level settings to
-  define database connections will be removed.
-
-* The ability to use shorthand notation to specify a database backend
-  (i.e., ``sqlite3`` instead of ``django.db.backends.sqlite3``) will be
-  removed.
-
-* The ``get_db_prep_save``, ``get_db_prep_value`` and
-  ``get_db_prep_lookup`` methods will have to support multiple databases.
-
-* The ``Message`` model (in ``django.contrib.auth``), its related
-  manager in the ``User`` model (``user.message_set``), and the
-  associated methods (``user.message_set.create()`` and
-  ``user.get_and_delete_messages()``), will be removed.  The
-  :doc:`messages framework </ref/contrib/messages>` should be used
-  instead. The related ``messages`` variable returned by the
-  auth context processor will also be removed. Note that this
-  means that the admin application will depend on the messages
-  context processor.
-
-* Authentication backends will need to support the ``obj`` parameter for
-  permission checking. The ``supports_object_permissions`` attribute
-  will no longer be checked and can be removed from custom backends.
-
-* Authentication backends will need to support the ``AnonymousUser`` class
-  being passed to all methods dealing with permissions.  The
-  ``supports_anonymous_user`` variable will no longer be checked and can be
-  removed from custom backends.
-
-* The ability to specify a callable template loader rather than a
-  ``Loader`` class will be removed, as will the ``load_template_source``
-  functions that are included with the built in template loaders for
-  backwards compatibility.
-
-* ``django.utils.translation.get_date_formats()`` and
-  ``django.utils.translation.get_partial_date_formats()``. These functions
-  will be removed; use the locale-aware
-  ``django.utils.formats.get_format()`` to get the appropriate formats.
-
-* In ``django.forms.fields``, the constants: ``DEFAULT_DATE_INPUT_FORMATS``,
-  ``DEFAULT_TIME_INPUT_FORMATS`` and
-  ``DEFAULT_DATETIME_INPUT_FORMATS`` will be removed. Use
-  ``django.utils.formats.get_format()`` to get the appropriate
-  formats.
-
-* The ability to use a function-based test runners will be removed,
-  along with the ``django.test.simple.run_tests()`` test runner.
-
-* The ``views.feed()`` view and ``feeds.Feed`` class in
-  ``django.contrib.syndication`` will be removed. The class-based view
-  ``views.Feed`` should be used instead.
-
-* ``django.core.context_processors.auth``.  This release will
-  remove the old method in favor of the new method in
-  ``django.contrib.auth.context_processors.auth``.
-
-* The ``postgresql`` database backend will be removed, use the
-  ``postgresql_psycopg2`` backend instead.
-
-* The ``no`` language code will be removed and has been replaced by the
-  ``nb`` language code.
-
-* Authentication backends will need to define the boolean attribute
-  ``supports_inactive_user`` until version 1.5 when it will be assumed that
-  all backends will handle inactive users.
-
-* ``django.db.models.fields.XMLField`` will be removed. This was
-  deprecated as part of the 1.3 release. An accelerated deprecation
-  schedule has been used because the field hasn't performed any role
-  beyond that of a simple ``TextField`` since the removal of oldforms.
-  All uses of ``XMLField`` can be replaced with ``TextField``.
-
-* The undocumented ``mixin`` parameter to the ``open()`` method of
-  ``django.core.files.storage.Storage`` (and subclasses) will be removed.
-
-
 1.5
 ---