From 66c0c58cf2bc08233ca7bd1d4973e34cbc2ab2ec Mon Sep 17 00:00:00 2001 From: Carlton Gibson Date: Wed, 25 Jul 2018 10:59:07 +0200 Subject: [PATCH] [2.1.x] Fixed #29593 -- Added QUERY_TERMS removal to 2.1 release notes. Removed in 244cc401559e924355cf943b6b8e66ccf2f6da3a. Backport of 5180015051f262b73559bb55a8e3fe6f551f8b68 from master --- docs/releases/2.1.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/releases/2.1.txt b/docs/releases/2.1.txt index fb0ffc3b89..89bcb46045 100644 --- a/docs/releases/2.1.txt +++ b/docs/releases/2.1.txt @@ -393,6 +393,13 @@ Miscellaneous * Management commands no longer allow the abbreviated forms of the ``--settings`` and ``--pythonpath`` arguments. +* The private ``django.db.models.sql.constants.QUERY_TERMS`` constant is + removed. The :meth:`~.RegisterLookupMixin.get_lookup` + and :meth:`~.RegisterLookupMixin.get_lookups` methods + of the :ref:`Lookup Registration API ` may be + suitable alternatives. Compared to the ``QUERY_TERMS`` constant, they allow + your code to also account for any custom lookups that have been registered. + .. _deprecated-features-2.1: Features deprecated in 2.1