cpython/Doc/library/abc.rst

167 lines
6.1 KiB
ReStructuredText
Raw Normal View History

:mod:`abc` --- Abstract Base Classes
====================================
.. module:: abc
:synopsis: Abstract base classes according to PEP 3119.
.. moduleauthor:: Guido van Rossum
.. sectionauthor:: Georg Brandl
.. much of the content adapted from docstrings
This module provides the infrastructure for defining abstract base classes
2007-09-04 15:45:25 +00:00
(ABCs) in Python, as outlined in :pep:`3119`; see there for a rationale why this
was added to Python.
Concrete base ABCs to derive from can be found in the :mod:`collections` module.
The module provides the following class:
.. class:: ABCMeta
Metaclass for defining Abstract Base Classes (ABCs).
Use this metaclass to create an ABC. An ABC can be subclassed directly, and
then acts as a mix-in class. You can also register unrelated concrete
classes (even built-in classes) and unrelated ABCs as "virtual subclasses" --
these and their descendants will be considered subclasses of the registering
ABC by the built-in :func:`issubclass` function, but the registering ABC
won't show up in their MRO (Method Resolution Order) nor will method
implementations defined by the registering ABC be callable (not even via
:func:`super`).
Classes created with a metaclass of :class:`ABCMeta` have the following method:
.. method:: register(subclass)
Register *subclass* as a "virtual subclass" of this ABC. From now on,
``issubclass(subclass, ABC)`` is true.
You can also override this method in an abstract base class:
.. method:: __subclasshook__(subclass)
(Must be defined as a class method.)
Check whether *subclass* is considered a subclass of this ABC. This means
that you can customize the behavior of ``issubclass`` further without the
need to call :meth:`register` on every class you want to consider a
2007-09-04 15:45:25 +00:00
subclass of the ABC. (This class method is called from the
:meth:`__subclasscheck__` method of the ABC.)
This method should return ``True``, ``False`` or ``NotImplemented``. If
it returns ``True``, the *subclass* is considered a subclass of this ABC.
If it returns ``False``, the *subclass* is not considered a subclass of
this ABC, even if it would normally be one. If it returns
``NotImplemented``, the subclass check is continued with the usual
mechanism.
2007-09-04 15:45:25 +00:00
.. XXX explain the "usual mechanism"
2007-09-04 15:45:25 +00:00
For a demonstration of these concepts, look at this example ABC definition::
2007-09-04 15:45:25 +00:00
class Foo:
def __getitem__(self, index):
...
def __len__(self):
...
def get_iterator(self):
return iter(self)
2007-09-04 15:45:25 +00:00
class MyIterable(metaclass=ABCMeta):
2007-09-04 15:45:25 +00:00
@abstractmethod
def __iter__(self):
2007-09-04 15:45:25 +00:00
while False:
yield None
def get_iterator(self):
return self.__iter__()
@classmethod
def __subclasshook__(cls, C):
2007-09-04 15:45:25 +00:00
if cls is MyIterable:
if any("__iter__" in B.__dict__ for B in C.__mro__):
return True
return NotImplemented
2007-09-04 15:45:25 +00:00
MyIterable.register(Foo)
2007-09-04 15:45:25 +00:00
The ABC ``MyIterable`` defines the standard iterable method,
:meth:`__iter__`, as an abstract method. The implementation given here can
still be called from subclasses. The :meth:`get_iterator` method is also
part of the ``MyIterable`` abstract base class, but it does not have to be
overridden in a non-abstract child.
The :meth:`__subclasshook__` class method defined here says that any class
2007-09-04 15:45:25 +00:00
that has an :meth:`__iter__` method in its :attr:`__dict__` (or in that of
one of its subclasses, accessed via the :attr:`__mro__`) is considered a
``MyIterable`` too.
2007-09-04 15:45:25 +00:00
Finally, the last line makes ``Foo`` a virtual subclass of ``MyIterable``,
even though it does not define a :meth:`__iter__` method (it uses the
old-style iterable protocol, defined in terms of :meth:`__len__` and
:meth:`__getitem__`). Note that this will not make ``get_iterator``
available as a method of ``Foo``, so it is provided separately.
It also provides the following decorators:
.. function:: abstractmethod(function)
A decorator indicating abstract methods.
2007-09-04 15:45:25 +00:00
Using this decorator requires that the metaclass is :class:`ABCMeta` or
derived from it. A class that has a metaclass derived from :class:`ABCMeta`
cannot be instantiated unless all of its abstract methods are overridden.
The abstract methods can be called using any of the the normal 'super' call
mechanisms.
Dynamically adding abstract methods to a class, or attempting to modify the
abstraction status of a method or class once it is created, are not
supported. The :func:`abstractmethod` only affects subclasses derived using
regular inheritance; "virtual subclasses" registered with the ABC's
:meth:`register` method are not affected.
Usage::
class C(metaclass=ABCMeta):
@abstractmethod
def my_abstract_method(self, ...):
...
2007-09-04 15:45:25 +00:00
.. note::
Unlike C++ or Java, these abstract methods may have an implementation.
This implementation can be called via the :func:`super` mechanism from the
class that overrides it. This could be useful as an end-point for a
super-call in framework using a cooperative multiple-inheritance
2007-09-04 15:45:25 +00:00
.. function:: abstractproperty(fget[, fset[, fdel[, doc]]])
2007-09-04 15:45:25 +00:00
A subclass of the built-in :func:`property`, indicating an abstract property.
Requires that the metaclass is :class:`ABCMeta` or derived from it. A class
that has a metaclass derived from :class:`ABCMeta` cannot be instantiated
unless all of its abstract properties are overridden. The abstract
properties can be called using any of the the normal 'super' call mechanisms.
Usage::
class C(metaclass=ABCMeta):
@abstractproperty
def my_abstract_property(self):
...
This defines a read-only property; you can also define a read-write abstract
property using the 'long' form of property declaration::
class C(metaclass=ABCMeta):
def getx(self): ...
def setx(self, value): ...
x = abstractproperty(getx, setx)