why should dict not be callable?

[georgeryoung@gmail.com]

A couple of times recently I've come across this problem: I have a
large list to sort and I need to the the "key=functi on" argument to
sort appropriately. But I actually have the key mapping in a big
dictionary. Now I have to make an intermediary function:

def key_fn(key):
return key_dict[key]

If a dict were callable directly, this would be unnecessary. Often the
small extra complexity and compute time is not important, but in
sorting a large list, it could be a significant difference. Is there
some reason a subscriptable thing like a dict should *not* be callable?


-- George [nitpicking...]

[Brett Hoerner]

Re: why should dict not be callable?

georgeryo...@gm ail.com wrote:

A couple of times recently I've come across this problem: I have a
large list to sort and I need to the the "key=functi on" argument to
sort appropriately. But I actually have the key mapping in a big
dictionary.

Is this what you mean? I suppose the lambda is an "intermedia ry
function" ... but meh...

l = ['bob', 'dog', 'cat', 'apple']
d = {'bob': 7, 'dog': 0, 'cat': 14, 'apple': 3}

l.sort(lambda x,y: d[x] - d[y])

print l
['dog', 'apple', 'bob', 'cat']

[Kent Johnson]

Re: why should dict not be callable?

georgeryoung@gm ail.com wrote:

A couple of times recently I've come across this problem: I have a
large list to sort and I need to the the "key=functi on" argument to
sort appropriately. But I actually have the key mapping in a big
dictionary. Now I have to make an intermediary function:
>
def key_fn(key):
return key_dict[key]

Try key=key_dict.__ getitem__

In [3]: d=dict(a=1,b=2)

In [4]: d.__getitem__(' a')
Out[4]: 1

Kent

[Robert Kern]

Re: why should dict not be callable?

georgeryoung@gm ail.com wrote:

A couple of times recently I've come across this problem: I have a
large list to sort and I need to the the "key=functi on" argument to
sort appropriately. But I actually have the key mapping in a big
dictionary. Now I have to make an intermediary function:
>
def key_fn(key):
return key_dict[key]
>
If a dict were callable directly, this would be unnecessary. Often the
small extra complexity and compute time is not important, but in
sorting a large list, it could be a significant difference. Is there
some reason a subscriptable thing like a dict should *not* be callable?

Because you can pass key_dict.get instead. Or even key_dict.__geti tem__ if you
don't want the default=None behavior of the .get() method.

--
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though it had
an underlying truth."
-- Umberto Eco

[Fredrik Lundh]

Re: why should dict not be callable?

georgeryoung@gm ail.com wrote:

A couple of times recently I've come across this problem: I have a
large list to sort and I need to the the "key=functi on" argument to
sort appropriately. But I actually have the key mapping in a big
dictionary.

so use a bound method:

L.sort(key=key_ dict.get)

</F>

[georgeryoung@gmail.com]

Re: why should dict not be callable?

On Oct 17, 3:37 pm, Fredrik Lundh <fred...@python ware.comwrote:

georgeryo...@gm ail.com wrote:

A couple of times recently I've come across this problem: I have a
large list to sort and I need to the the "key=functi on" argument to
sort appropriately. But I actually have the key mapping in a big
dictionary.so use a bound method:

>
L.sort(key=key_ dict.get)

Duh! Why didn't I think of that... Thanks guys, that's perfect.

-- George