This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients eric.araujo, flox, ncoghlan, rhettinger
Date 2010-08-09.05:51:00
SpamBayes Score 2.80546e-05
Marked as misclassified No
Message-id <>
In-reply-to <>
On Mon, Aug 9, 2010 at 3:11 PM, Raymond Hettinger
<> wrote:
> ISTM, we should just provide basic caching with reasonable space consumption (i.e. not huge) that gives improvements to common use cases (like I've done with the fnmatch and re module) and let programmers with unusual cases add their own caching options rather that be tied into our choice of lru vs lfu or whatnot.

A very good point! Perhaps we should note that somewhere? I'm not sure
where though, unless we just mention it in the docs for the relevant

Going the other way (using a smaller, or no, cache), perhaps in
addition to the new hit/miss attributes, the cache decorators should
expose the original function to allow the cache to be bypassed?
Date User Action Args
2010-08-09 05:51:04ncoghlansetrecipients: + ncoghlan, rhettinger, eric.araujo, flox
2010-08-09 05:51:02ncoghlanlinkissue9396 messages
2010-08-09 05:51:00ncoghlancreate