From 663af270b58f350bcbd9df5cd04ffe69e8ac37c8 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Wed, 23 Jul 2014 15:23:36 -0400 Subject: [PATCH] [1.7.x] Added backwards incompatibility note for refs #22845; refs #23082. Thanks Kyle Owens for the report. Backport of 8568e7cfa4 from master --- docs/releases/1.7.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt index 1cac7edb56..105388fdb7 100644 --- a/docs/releases/1.7.txt +++ b/docs/releases/1.7.txt @@ -1405,6 +1405,16 @@ Miscellaneous method that is registered with the check framework. If you have an existing method called ``check()`` on one of these objects, you will need to rename it. +* As noted above in the "Cache" section of "Minor Features", defining the + :setting:`TIMEOUT ` argument of the + :setting:`CACHES` setting as ``None`` will set the cache keys as + "non-expiring". Previously, with the memcache backend, a + :setting:`TIMEOUT ` of ``0`` would set non-expiring keys, + but this was inconsistent with the set-and-expire (i.e. no caching) behavior + of ``set("key", "value", timeout=0)``. If you want non-expiring keys, + please update your settings to use ``None`` instead of ``0`` as the latter + now designates set-and-expire in the settings as well. + .. _deprecated-features-1.7: Features deprecated in 1.7