From ec7e179aeb177a2a43b448b30d9286eb8539be8d Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Thu, 27 Dec 2018 19:17:23 -0500 Subject: Removed versionadded/changed annotations for 2.1. --- docs/howto/custom-lookups.txt | 5 ----- docs/howto/custom-management-commands.txt | 6 ------ 2 files changed, 11 deletions(-) (limited to 'docs/howto') diff --git a/docs/howto/custom-lookups.txt b/docs/howto/custom-lookups.txt index 1e73d329e7..7504997ed5 100644 --- a/docs/howto/custom-lookups.txt +++ b/docs/howto/custom-lookups.txt @@ -148,11 +148,6 @@ And on databases that support distinct on fields (such as PostgreSQL), SELECT ... DISTINCT ON ABS("experiments"."change") -.. versionchanged:: 2.1 - - Ordering and distinct support as described in the last two paragraphs was - added. - When looking for which lookups are allowable after the ``Transform`` has been applied, Django uses the ``output_field`` attribute. We didn't need to specify this here as it didn't change, but supposing we were applying ``AbsoluteValue`` diff --git a/docs/howto/custom-management-commands.txt b/docs/howto/custom-management-commands.txt index d547bd97e2..aeee00016a 100644 --- a/docs/howto/custom-management-commands.txt +++ b/docs/howto/custom-management-commands.txt @@ -144,12 +144,6 @@ decorator on your :meth:`~BaseCommand.handle` method:: Since translation deactivation requires access to configured settings, the decorator can't be used for commands that work without configured settings. -.. versionchanged:: 2.1 - - The ``@no_translations`` decorator is new. In older versions, translations - are deactivated before running a command unless the command's - ``leave_locale_alone`` attribute (now removed) is set to ``True``. - Testing ======= -- cgit v1.3