From a2e927b7ed25bd319f866c55b18cd214a149d859 Mon Sep 17 00:00:00 2001 From: Mike Grouchy Date: Wed, 18 Jul 2012 08:00:31 -0400 Subject: BaseCache now has a no-op close method as per ticket #18582 Also removed the hasattr check when firing request_finished signal for caches with a 'close' method. Should be safe to call `cache.close` everywhere now --- docs/topics/cache.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'docs') diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt index 03afa86647..85f4c64aa8 100644 --- a/docs/topics/cache.txt +++ b/docs/topics/cache.txt @@ -779,6 +779,16 @@ nonexistent cache key.:: However, if the backend doesn't natively provide an increment/decrement operation, it will be implemented using a two-step retrieve/update. + +You can close the connection to your cache with ``close()`` if implemented by +the cache backend. + + >>> cache.close() + +.. note:: + + For caches that don't implement ``close`` methods it is a no-op. + .. _cache_key_prefixing: Cache key prefixing -- cgit v1.3