[Python-Dev] weakref enhancements (original) (raw)
Bob Ippolito bob at redivi.com
Fri Sep 29 03:13:14 CEST 2006
- Previous message: [Python-Dev] weakref enhancements
- Next message: [Python-Dev] weakref enhancements
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 9/28/06, Raymond Hettinger <raymond.hettinger at verizon.net> wrote:
> There are definitely use cases for keeping bound methods around. > > Contrived example: > > oneof = set([1,2,3,4]).contains > filter(oneof, [2,4,6,8,10])
ISTM, the example shows the (undisputed) utility of regular bound methods. How does it show the need for methods bound weakly to the underlying object, where the underlying can be deleted while the bound method persists, alive but unusable?
It doesn't. I seem to have misinterpreted your "Weakmethods have some use (...)" sentence. Sorry for the noise.
-bob
- Previous message: [Python-Dev] weakref enhancements
- Next message: [Python-Dev] weakref enhancements
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]