18

Say I have the following abstract class Foo:

import abc

class Foo(abc.ABC):

    @abc.abstractmethod
    def bar(self):
        raise NotImplementedError

What should I put in the body of the bar method?

I see a lot of code that has raise NotImplementedError, as shown above. However, this seems redundant, since any subclass that does not implement bar will raise the TypeError: Can't instantiate abstract class Foo with abstract methods bar when it is instantiated.

Is it Pythonic to leave bar empty, as follows:

import abc

class Foo(abc.ABC):

    @abc.abstractmethod
    def bar(self):
        ...

This is what is done in the Python docs for Abstract Base Classes, but I'm not sure if that's just a placeholder or an actual example of how to write code.

If it's ok to leave bar with only three dots (...), when should I use NotImplementedError?

martineau
  • 112,593
  • 23
  • 157
  • 280
ostrokach
  • 14,836
  • 7
  • 69
  • 87

1 Answers1

15

The documentation does aim to give you an example. You don't have to follow it.

You could provide a default; subclasses are still free to use super() to call your implementation. This is what most of the collections.abc classes do; see the source code.

Size for example, returns 0 for __len__:

class Sized(metaclass=ABCMeta):
    # ...
    @abstractmethod
    def __len__(self):
        return 0
Martijn Pieters
  • 963,270
  • 265
  • 3,804
  • 3,187
  • 2
    Thanks for the link. [MutableSet.add](https://hg.python.org/cpython/file/3.5/Lib/_collections_abc.py#l508) and [MutableSet.discard](https://hg.python.org/cpython/file/3.5/Lib/_collections_abc.py#l513) do raise `NotImplementedError`, so I guess I should stick with that convention instead of `...`. – ostrokach Nov 30 '16 at 17:23