[issue9396] Standardise (and publish?) cache handling in standard library

Éric Araujo added the comment: Raymond, out of curiosity, can you tell why you removed lfu_cache? -- ___ Python tracker ___ ___ Python

[issue9396] Standardise (and publish?) cache handling in standard library

Changes by Raymond Hettinger : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue9396] Standardise (and publish?) cache handling in standard library

Nick Coghlan added the comment: Have we had any luck getting this to play nicely with the buildbots yet? (I lost track of where the last checkin got to). The necessary Modules/Setup change to adjust when _collections is built should have propagated through by now. -- ___

[issue9396] Standardise (and publish?) cache handling in standard library

Éric Araujo added the comment: After discussion with RDM on IRC, I’m opening a new report to track this feature request separately. (It’s also a dependency of this bug.) -- assignee: r.david.murray -> rhettinger dependencies: +Add attribute pointing to wrapped function to partial objec

[issue9396] Standardise (and publish?) cache handling in standard library

Raymond Hettinger added the comment: Great minds think alike. I was just about to propose that functools.wraps add a standard attribute to point at the underlying function (on the theory that objects should be introspectable). This would allow a standard way to get to the underlying unwrapp

[issue9396] Standardise (and publish?) cache handling in standard library

Nick Coghlan added the comment: 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 progr

[issue9396] Standardise (and publish?) cache handling in standard library

Raymond Hettinger added the comment: I was thinking about the problem of developers wanting a different cache size than that provided in standard lib modules. ISTM that now we've offered caching abilities in functools, a developer can easily add another layer of cache around any API they are

[issue9396] Standardise (and publish?) cache handling in standard library

Nick Coghlan added the comment: On Mon, Aug 9, 2010 at 2:29 PM, Raymond Hettinger wrote: > I did find a simple way to dynamically resize the maxcache, but did not apply > it yet.   Will look at more applications to see if it is really needed. > > Nick, thanks for the great ideas.  These change

[issue9396] Standardise (and publish?) cache handling in standard library

Raymond Hettinger added the comment: Applied the lru_cache() to fnmatch and re. See r83874 r83871. I did find a simple way to dynamically resize the maxcache, but did not apply it yet. Will look at more applications to see if it is really needed. Nick, thanks for the great ideas. These cha

[issue9396] Standardise (and publish?) cache handling in standard library

Changes by Éric Araujo : -- nosy: +merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue9396] Standardise (and publish?) cache handling in standard library

Nick Coghlan added the comment: Yeah, I'm not sure the dynamic resizing makes sense in general. I was just pointing it out as something supported by the existing caches that could complicate a consolidation effort. -- ___ Python tracker

[issue9396] Standardise (and publish?) cache handling in standard library

Changes by Raymond Hettinger : -- assignee: -> rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue9396] Standardise (and publish?) cache handling in standard library

Raymond Hettinger added the comment: I will take a look at the various caches and see if some of their features can be consolidated. It is okay if some need to have their own strategies or situation specific approaches, but you're right that common features should be looked at to see if they

[issue9396] Standardise (and publish?) cache handling in standard library

Nick Coghlan added the comment: With Raymond adding functools.lru_cache and functools.lfu_cache, it should be possible to use those for the various caches in the standard library. My only point of concern is that the standard lib caches tend to allow dynamic modification of the max cache size

[issue9396] Standardise (and publish?) cache handling in standard library

Changes by Antoine Pitrou : -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue9396] Standardise (and publish?) cache handling in standard library

Changes by Florent Xicluna : -- nosy: +flox ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue9396] Standardise (and publish?) cache handling in standard library

New submission from Nick Coghlan : The standard library has several cache implementations (e.g. in re, fnmatch and ElementTree) with different cache size limiting strategies. These should be standardised and possibly even exposed for general use. Refer to python-dev discussion: http://mail.pyt