Django/django
11
0
Fork 0
Code Pull Requests Projects Releases Activity

[2.1.x] Fixed #29593 -- Added QUERY_TERMS removal to 2.1 release notes.

Browse Source 
Removed in 244cc401559e924355cf943b6b8e66ccf2f6da3a.

Backport of 5180015051f262b73559bb55a8e3fe6f551f8b68 from master
This commit is contained in:
Carlton Gibson 2018-07-25 10:59:07 +02:00 committed by Simon Charette
parent 2b19d198b1
commit 66c0c58cf2
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/releases/2.1.txt
View File

@ -393,6 +393,13 @@ Miscellaneous
* Management commands no longer allow the abbreviated forms of the * Management commands no longer allow the abbreviated forms of the
``--settings`` and ``--pythonpath`` arguments. ``--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 <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: .. _deprecated-features-2.1:
Features deprecated in 2.1 Features deprecated in 2.1