> > I am ok with renaming lazy_cache (although some people will ask, isn't the > cache lazy already by definition?). We cannot call it current_cache because > it is not current.cache and that would cause confusion. It is a lazy > current.cache. >
I was thinking current_cache because it's a decorator that uses current.cache. We can use current.cache in a module, but we can't decorate with @current.cache, so I was thinking the next closest thing would be @current_cache (which uses current.cache internally anyway). Anthony --
