Subclassing Python dictionary to override __setitem__ Subclassing Python dictionary to override __setitem__ python python

Subclassing Python dictionary to override __setitem__


I'm answering my own question, since I eventually decided that I really do want to subclass Dict, rather than creating a new mapping class, and UserDict still defers to the underlying Dict object in some cases, rather than using the provided __setitem__.

After reading and re-reading the Python 2.6.4 source (mostly Objects/dictobject.c, but I grepped eveywhere else to see where the various methods are used,) my understanding is that the following code is sufficient to have my __setitem__ called every time that the object is changed, and to otherwise behave exactly as a Python Dict:

Peter Hansen's suggestion got me to look more carefully at dictobject.c, and I realised that the update method in my original answer could be simplified a bit, since the built-in dictionary constructor simply calls the built-in update method anyway. So the second update in my answer has been added to the code below (by some helpful person ;-).

class MyUpdateDict(dict):    def __init__(self, *args, **kwargs):        self.update(*args, **kwargs)    def __setitem__(self, key, value):        # optional processing here        super(MyUpdateDict, self).__setitem__(key, value)    def update(self, *args, **kwargs):        if args:            if len(args) > 1:                raise TypeError("update expected at most 1 arguments, "                                "got %d" % len(args))            other = dict(args[0])            for key in other:                self[key] = other[key]        for key in kwargs:            self[key] = kwargs[key]    def setdefault(self, key, value=None):        if key not in self:            self[key] = value        return self[key]

I've tested it with this code:

def test_updates(dictish):    dictish['abc'] = 123    dictish.update({'def': 234})    dictish.update(red=1, blue=2)    dictish.update([('orange', 3), ('green',4)])    dictish.update({'hello': 'kitty'}, black='white')    dictish.update({'yellow': 5}, yellow=6)    dictish.setdefault('brown',7)    dictish.setdefault('pink')    try:        dictish.update({'gold': 8}, [('purple', 9)], silver=10)    except TypeError:        pass    else:        raise RunTimeException("Error did not occur as planned")python_dict = dict([('b',2),('c',3)],a=1)test_updates(python_dict)my_dict = MyUpdateDict([('b',2),('c',3)],a=1)test_updates(my_dict)

and it passes. All other implementations I've tried have failed at some point. I'll still accept any answers that show me that I've missed something, but otherwise, I'm ticking the checkmark beside this one in a couple of days, and calling it the right answer :)


What is your use-case for subclassing dict?

You don't need to do this to implement a dict-like object, and it might be simpler in your case to write an ordinary class, then add support for the required subset of the dict interface.

The best way to accomplish what you're after is probably the MutableMapping abstract base class. PEP 3119 -- Introducing Abstract Base Classes

This will also help you anser the question "Are there any other methods which I need to override?". You will need to override all the abstract methods. For MutableMapping: Abstract methods include setitem, delitem. Concrete methods include pop, popitem, clear, update.


I found Ian answer and comments very helpful and clear. I would just point out that maybe a first call to the super-class __init__ method might be safer, when not necessary: I recently needed to implement a custom OrderedDict (I'm working with Python 2.7): after implementing and modifying my code according to the proposed MyUpdateDict implementation, I found out that by simply replacing

class MyUpdateDict(dict):

with:

from collections import OrderedDictclass MyUpdateDict(OrderedDict):

then the test code posted above failed:

Traceback (most recent call last):File "Desktop/test_updates.py", line 52, in <module>    my_dict = MyUpdateDict([('b',2),('c',3)],a=1)File "Desktop/test_updates.py", line 5, in __init__    self.update(*args, **kwargs)File "Desktop/test_updates.py", line 18, in update    self[key] = other[key]File "Desktop/test_updates.py", line 9, in __setitem__    super(MyUpdateDict, self).__setitem__(key, value)File "/usr/lib/python2.7/collections.py", line 59, in __setitem__    root = self.__rootAttributeError: 'MyUpdateDict' object has no attribute '_OrderedDict__root'

Looking at collections.py code it turns out that OrderedDict needs its __init__ method to be called in order to initialize and setup necessary custom attributes.

Therefore, by simply adding a first call to the super __init__ method,

from collections import OrderedDictclass MyUpdateDict(Orderedict):def __init__(self, *args, **kwargs):    super(MyUpdateDict, self).__init__() #<-- HERE call to super __init__    self.update(*args, **kwargs)

we have a more general solution which apparently works for both dict and OrderedDict.

I cannot state if this solution is generally valid, because I tested it with OrderedDict only. However, it is likely that a call to the super __init__ method is either harmless or necessary rather than harmful, when trying to extend other dict subclasses