Remove some lingering remnants of the short-lived functools.lfu_cache
This commit is contained in:
parent
ad1e0c5e5f
commit
632a0c1476
|
@ -36,33 +36,6 @@ The :mod:`functools` module defines the following functions:
|
|||
|
||||
.. versionadded:: 3.2
|
||||
|
||||
.. decorator:: lfu_cache(maxsize)
|
||||
|
||||
Decorator to wrap a function with a memoizing callable that saves up to the
|
||||
*maxsize* most frequent calls. It can save time when an expensive or I/O
|
||||
bound function is periodically called with the same arguments.
|
||||
|
||||
The *maxsize* parameter defaults to 100. Since a dictionary is used to cache
|
||||
results, the positional and keyword arguments to the function must be
|
||||
hashable.
|
||||
|
||||
The wrapped function is instrumented with two attributes, :attr:`hits`
|
||||
and :attr:`misses` which count the number of successful or unsuccessful
|
||||
cache lookups. These statistics are helpful for tuning the *maxsize*
|
||||
parameter and for measuring the cache's effectiveness.
|
||||
|
||||
The wrapped function also has a :attr:`clear` attribute which can be
|
||||
called (with no arguments) to clear the cache.
|
||||
|
||||
A `LFU (least frequently used) cache
|
||||
<http://en.wikipedia.org/wiki/Cache_algorithms#Least-Frequently_Used>`_
|
||||
is indicated when the pattern of calls does not change over time, when
|
||||
more the most common calls already seen are the best predictors of the
|
||||
most common upcoming calls (for example, a phonelist of popular
|
||||
help-lines may have access patterns that persist over time).
|
||||
|
||||
.. versionadded:: 3.2
|
||||
|
||||
.. decorator:: lru_cache(maxsize)
|
||||
|
||||
Decorator to wrap a function with a memoizing callable that saves up to the
|
||||
|
|
Loading…
Reference in New Issue