Message133300
I've looked at the code for Python 3, and there isn't anything there that
prevents this from happening there, either. So the fix should be applied
to 3.2 and 3.3 as well.
An alternative approach would be to limit the size of the cache, so that
the caller doesn't need to explicitly clear the cache. Something along
the lines of functools.lru_cache() should do the trick. I don't think
it'll be possible to use lru_cache() itself, though - it doesn't provide
a mechanism to invalidate cache entries when they become stale (and in
any case, it doesn't exist in 2.7). |
|
Date |
User |
Action |
Args |
2011-04-08 09:16:43 | nadeem.vawda | set | recipients:
+ nadeem.vawda, lopgok |
2011-04-08 09:16:43 | nadeem.vawda | set | messageid: <1302254203.38.0.743728960326.issue11802@psf.upfronthosting.co.za> |
2011-04-08 09:16:42 | nadeem.vawda | link | issue11802 messages |
2011-04-08 09:16:41 | nadeem.vawda | create | |
|