[Python-Dev] Should we do away with unbound methods in Py3k?
Greg Ewing
greg.ewing at canterbury.ac.nz
Sat Nov 24 00:38:54 CET 2007
More information about the Python-Dev mailing list
Sat Nov 24 00:38:54 CET 2007
- Previous message: [Python-Dev] Should we do away with unbound methods in Py3k?
- Next message: [Python-Dev] Should we do away with unbound methods in Py3k?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Phillip J. Eby wrote: > class MoneyField(Field): > # does need staticmethod because two_decimal_places > # doesn't take a self > converter = staticmethod(two_decimal_places) Okay, I see what you mean now. But you could just as well wrap it in a function that takes self and discards it, so I still don't think staticmethod is essential in the absence of unbound methods. Not that I would object if it stayed around -- I don't really mind one way or the other. -- Greg
- Previous message: [Python-Dev] Should we do away with unbound methods in Py3k?
- Next message: [Python-Dev] Should we do away with unbound methods in Py3k?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list