_{^{This is not production ready! There are still likely many bugs and there are several performance improvements which can be made}}

Introducing smart cache—apply the @smart_cache decorator and all inputs with the same hash will be cached cross-run. Furthermore, the cache will be invalidated if the method bytecode OR the bytecode of method dependencies changes. This allows for fast rapid prototyping. You do not have to focus on which functions have been changed, Smart Cache does the work for you.

The only thing to pay attention to is that your functions are pure! This _^basically means that the same input arguments will always yield the same result. If this isn't the case, then don't include the @smart_cache decorator on that function—it can't be cached!

pip3 install smart-cache

Make sure to execute

export PYTHONHASHSEED=0

as hashes are by default salted.

Let's benchmark the times between cached and non-cached versions of recursive fibonacci.

@smart_cache def fib(n): if n == 0: return 0 if n == 1: return 1 return fib(n - 1) + fib(n - 2) def bad_fib(n): if n == 0: return 0 if n == 1: return 1 return bad_fib(n - 1) + bad_fib(n - 2) if __name__ == "__main__": start = time.time() cached_result = fib(40) end = time.time() print("total time cached: {:.2f}ms".format((end - start) * 1000)) start = time.time() actual_result = bad_fib(40) end = time.time() print("total time uncached: {:.2f}ms".format((end - start) * 1000)) difference = actual_result - cached_result print("difference: ", difference)

The first run (without any previous caching) we get times of

total time cached: 0.58ms total time uncached: 31840.58ms difference: 0 

The second time will be even faster—we only need one lookup since fib(40) is cached. We get

total time cached: 0.48ms total time uncached: 31723.69ms difference: 0 

Suppose we run

def abc(): x = 2+2 return x @smart_cache def tester(): return 1 + abc() if __name__ == "__main__": print(tester())

Only the first time we run this will results not be cached.

Suppose we make a modification to abc

def abc(): x = 2+3 return x

All caches will be invalidated. However, if abc were changed to

def abc(): # this is a comment x = 2+2 return x

The cache will not be invalidated because even though the code changes—none of the byte code changes.

Similary if we add another function xyz(),

def xyz(a_param): return a_param*2

The cache will also NOT be invalidated because although the bytecode of the file changes, the bytecode of neither the function tester nor its dependencies change.

Recursive functions also work as expected!

@smart_cache def fib(n): if n == 0: return 0 if n == 1: return 1 return fib(n - 1) + fib(n - 2) if __name__ == "__main__": print(fib(6))

will run in O(n) time when it is first run and O(1) the time after that.