Lock.extend() can now replace the lock's existing TTL with a new value

Lock.extend() now has a new option, `replace_ttl`. When False (the
default), Lock.extend() adds the `additional_time` to the lock's existing
TTL. When replace_ttl=True, the lock's existing TTL is replaced with
the value of `additional_time`.

1 files changed, 4 insertions, 0 deletions

diff --git a/CHANGES b/CHANGES
index a3c4fcf..3670f6f 100644
--- a/CHANGES
+++ b/CHANGES
@@ -22,6 +22,10 @@
       a roundtrip to the server by not having to call UNWATCH within
       Pipeline.reset(). Thanks @nickgaya, #1299/#1302
     * Add the KEEPTTL option for the SET command. Thanks @laixintao #1304/#1280
+    * Lock.extend() now has a new option, `replace_ttl`. When False (the
+      default), Lock.extend() adds the `additional_time` to the lock's existing
+      TTL. When replace_ttl=True, the lock's existing TTL is replaced with
+      the value of `additional_time`.
 * 3.4.1
     * Move the username argument in the Redis and Connection classes to the
       end of the argument list. This helps those poor souls that specify all