From e47b56d791eb6c81c6d83529b7a068959ea1c1ec Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Sat, 2 Sep 2017 19:59:45 -0400 Subject: Refs #20892 -- Removed support for passing pylibmc behavior settings as top-level attributes of CACHES['OPTIONS']. Per deprecation timeline. --- docs/releases/2.1.txt | 3 +++ docs/topics/cache.txt | 8 -------- 2 files changed, 3 insertions(+), 8 deletions(-) (limited to 'docs') diff --git a/docs/releases/2.1.txt b/docs/releases/2.1.txt index 7f1330b756..1fd22da588 100644 --- a/docs/releases/2.1.txt +++ b/docs/releases/2.1.txt @@ -236,3 +236,6 @@ how to remove usage of these features. * ``django.test.runner.setup_databases()`` is removed. * ``django.utils.translation.string_concat()`` is removed. + +* ``django.core.cache.backends.memcached.PyLibMCCache`` no longer supports + passing ``pylibmc`` behavior settings as top-level attributes of ``OPTIONS``. diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt index 6e6564d3e2..16e9a63580 100644 --- a/docs/topics/cache.txt +++ b/docs/topics/cache.txt @@ -479,14 +479,6 @@ the binary protocol, SASL authentication, and the ``ketama`` behavior mode:: } } -.. versionchanged:: 1.11 - - Memcached backends can now be configured using ``OPTIONS``. - - In older versions, you could pass ``pylibmc`` behavior settings directly - inside ``OPTIONS``. This is deprecated in favor of setting them under a - ``behaviors`` key within ``OPTIONS`` instead. - .. _the-per-site-cache: The per-site cache -- cgit v1.3