On Thu, 2005-11-03 at 11:32 +0900, Trans wrote:
> Sorry I didn't respond directly to your last post. I was hoping to try
> the code out first, but my system is screwed up at them moment. Your
> example is interesting. I hadn't notice __getobj__ before. Also, I
> don't think caching is always desired. Better if it is setable, like
> using memoize on a method.

Any suggestions for what the interface for enabling/disabling caching
should look like?  I think I may as well roll this stuff into a library.

-mental