[Python-Dev] Should we do away with unbound methods in Py3k?
André Malo
nd at perlig.de
Sat Nov 24 19:06:30 CET 2007
More information about the Python-Dev mailing list
Sat Nov 24 19:06:30 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 ]
* Greg Ewing wrote: > 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, I always thought, that this is exactly what staticmethod does. > so I still > don't think staticmethod is essential in the absence of > unbound methods. Actually I don't see why those issues were bound together in the first place. nd -- Winnetous Erbe: <http://pub.perlig.de/books.html#apache2>
- 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