Raymond Hettinger <[EMAIL PROTECTED]> added the comment:
I had said "almost always". Sure, if you don't care about performance
or scalability, a key= argument would be a net win.
We're responsible for creating an API that steers most programmers in
the right direction (Tim sez "we read Knuth so you don't have to").
Algorithmically, the bisect functions are at the wrong level of
granularity for applying a key function.
For user-defined objects, there is no need for a key-attribute since can
just supply a custom comparison method:
class UserDefined:
. . .
def cmp(self, other):
return cmp(self.key, other.key)
_______________________________________
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4356>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
