On Jan 17, 2005, at 18:33, Glyph Lefkowitz wrote: > It's not the strongest use-case in the world, but is the impetus to > remove unbound method objects from Python that much stronger? I like > the fact that it's simpler, but it's a small amount of extra > simplicity, > it doesn't seem to enable any new use-cases, and it breaks the > potential > for serialization. Well, it lets you meaningfully do: class Foo: def someMethod(self): pass class Bar: someMethod = Foo.someMethod Where now you have to do: class Bar: someMethod = Foo.someMethod.im_func I'm not sure how useful this actually is, though. -bob
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4