> There are *definitely* use cases for keeping bound methods around. > > Contrived example: > > one_of = set([1,2,3,4]).__contains__ > filter(one_of, [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? Raymond _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
