diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/internals/deprecation.txt | 185 |
1 files changed, 0 insertions, 185 deletions
diff --git a/docs/internals/deprecation.txt b/docs/internals/deprecation.txt index 52dcd404ca..9577e53800 100644 --- a/docs/internals/deprecation.txt +++ b/docs/internals/deprecation.txt @@ -7,191 +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 runner 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 ---- - -See the :doc:`Django 1.3 release notes</releases/1.3>` for more details on -these changes. - -* Starting Django without a :setting:`SECRET_KEY` will result in an exception - rather than a ``DeprecationWarning``. (This is accelerated from the usual - deprecation path; see the :doc:`Django 1.4 release notes</releases/1.4>`.) - -* The ``mod_python`` request handler will be removed. The ``mod_wsgi`` - handler should be used instead. - -* The ``template`` attribute on :class:`~django.test.client.Response` - objects returned by the :ref:`test client <test-client>` will be removed. - The :attr:`~django.test.client.Response.templates` attribute should be - used instead. - -* The ``django.test.simple.DjangoTestRunner`` will be removed. - Instead use a unittest-native class. The features of the - ``django.test.simple.DjangoTestRunner`` (including fail-fast and - Ctrl-C test termination) can currently be provided by the unittest-native - :class:`~unittest.TextTestRunner`. - -* The undocumented function - ``django.contrib.formtools.utils.security_hash`` will be removed, - instead use ``django.contrib.formtools.utils.form_hmac`` - -* The function-based generic view modules will be removed in favor of their - class-based equivalents, outlined :doc:`here - </topics/class-based-views/index>`. - -* The ``django.core.servers.basehttp.AdminMediaHandler`` will be - removed. In its place use - ``django.contrib.staticfiles.handlers.StaticFilesHandler``. - -* The template tags library ``adminmedia`` and the template tag ``{% - admin_media_prefix %}`` will be removed in favor of the generic static files - handling. (This is faster than the usual deprecation path; see the - :doc:`Django 1.4 release notes</releases/1.4>`.) - -* The :ttag:`url` and :ttag:`ssi` template tags will be - modified so that the first argument to each tag is a template variable, not - an implied string. In 1.4, this behavior is provided by a version of the tag - in the ``future`` template tag library. - -* The ``reset`` and ``sqlreset`` management commands will be removed. - -* Authentication backends will need to support an inactive user - being passed to all methods dealing with permissions. - The ``supports_inactive_user`` attribute will no longer be checked - and can be removed from custom backends. - -* :meth:`~django.contrib.gis.geos.GEOSGeometry.transform` will raise - a :class:`~django.contrib.gis.geos.GEOSException` when called - on a geometry with no SRID value. - -* ``django.http.CompatCookie`` will be removed in favor of - ``django.http.SimpleCookie``. - -* ``django.core.context_processors.PermWrapper`` and - ``django.core.context_processors.PermLookupDict`` will be removed in - favor of the corresponding - ``django.contrib.auth.context_processors.PermWrapper`` and - ``django.contrib.auth.context_processors.PermLookupDict``, respectively. - -* The :setting:`MEDIA_URL` or :setting:`STATIC_URL` settings will be - required to end with a trailing slash to ensure there is a consistent - way to combine paths in templates. - -* ``django.db.models.fields.URLField.verify_exists`` will be removed. The - feature was deprecated in 1.3.1 due to intractable security and - performance issues and will follow a slightly accelerated deprecation - timeframe. - -* Translations located under the so-called *project path* will be ignored during - the translation building process performed at runtime. The - :setting:`LOCALE_PATHS` setting can be used for the same task by including the - filesystem path to a ``locale`` directory containing non-app-specific - translations in its value. - -* The Markup contrib app will no longer support versions of Python-Markdown - library earlier than 2.1. An accelerated timeline was used as this was - a security related deprecation. - -* The ``CACHE_BACKEND`` setting will be removed. The cache backend(s) should be - specified in the :setting:`CACHES` setting. - 1.6 --- |