I am working with two classes in Python, one of which should be allowed to have any number objects from another class as children while keeping an inventory of these children as an attribute. Inheritance seemed like the obvious choice for this parent<>child situation but instead what I have arrived at is an example of composition. Here is the simplified code:
class Parent:
def __init__(self, firstname, lastname):
self.firstname = firstname
self.lastname = lastname
self.kids = []
def havechild(self, firstname):
print(self.firstname, "is having a child")
self.kids.append(Child(self, firstname))
class Child(Parent):
def __init__(self, parent, firstname):
self.parent = parent
self.firstname = firstname
self.lastname = parent.lastname
So basically, while it seems to make intuitive sense to have Child() inherit from Parent(), removing the inheritance, does not change anything at all. The only benefit I can see for leaving Child(Parent) instead of just class Child() would be if I needed to add a lot more methods to Parent that I would like Child to inherit. Using the self.parent = parent, I already have access to any additional future attributes of the Parent.
Is there another way to use pure inheritance rather than passing the Parent instance into the Child constructor (composition)?
Composition enables you to reuse code by adding objects to other objects, as opposed to inheriting the interface and implementation of other classes. Both Horse and Dog classes can leverage the functionality of Tail through composition without deriving one class from the other.
Prefer composition over inheritance as it is more malleable / easy to modify later, but do not use a compose-always approach. With composition, it's easy to change behavior on the fly with Dependency Injection / Setters. Inheritance is more rigid as most languages do not allow you to derive from more than one type.
Inheritance and composition are two programming techniques developers use to establish relationships between classes and objects. Whereas inheritance derives one class from another, composition defines a class as the sum of its parts.
To favor composition over inheritance is a design principle that gives the design higher flexibility. It is more natural to build business-domain classes out of various components than trying to find commonality between them and creating a family tree.
It is definitely not good to inherint Child from Parent or Parent from Child.
The correct way to do it is to make a base class, let's say Person and inherit both Child and Parent from it.
An advantage of doing this is to remove code repetition, at the moment you have only firstname / lastname fields copied into both objects, but you may have more data or additional methods, like get_name()
to work with this data.
Here is an example:
class Person:
def __init__(self, firstname, lastname):
self.firstname = firstname
self.lastname = lastname
def get_name(self):
return f"{self.firstname} {self.lastname}"
class Parent(Person):
def __init__(self, firstname, lastname):
super().__init__(firstname, lastname)
self.kids = []
def havechild(self, firstname):
print(self.firstname, "is having a child")
self.kids.append(Child(self, firstname))
class Child(Person):
def __init__(self, parent, firstname):
super().__init__(firstname, parent.lastname)
self.parent = parent
Another way of doing this is to do it without inheritance, but only have one Person object (vs Parent and Child). The feature of tracking family status and parents / children can be moved into another object.
An advantage of this approach is that you follow the single responsibility principle and keep objects simple, each object does only one thing.
Here is an example:
from collections import defaultdict
class Person:
def __init__(self, firstname, lastname):
self.firstname = firstname
self.lastname = lastname
def get_name(self):
return f"{self.firstname} {self.lastname}"
class FamilyRegistry(object):
def __init__(self):
self.kids = defaultdict(list)
def register_birth(self, parent, child_name):
print(parent.firstname, "is having a child")
child = Person(child_name, parent.lastname)
self.kids[parent.lastname].append(child)
return child
def print_children(self, person):
children = self.kids[person.lastname]
if len(children) == 0:
print("{} has no children" % person.get_name())
return
for child in children:
print(child.get_name())
It works like this:
joe = Person('Joe', 'Black')
jill = Person('Jill', 'White')
registry = FamilyRegistry()
registry.register_birth(joe, 'Joe Junior') # Joe is having a child
registry.register_birth(joe, 'Tina') # Joe is having a child
registry.print_children(joe) # Joe Junior Black
# Tina Black
registry.print_children(jill) # Jill White has no children
First off, I think you are confusing things. As you yourself mention inheritance is used in a class that wants to inherit the nature of the parent class and then modify that behavior and extend it.
In your example Child inherits two things from Parent. The constructor __init__
and havechild
. You are overriding the constructor and the havechild
method shouldn't work, since there is no kids member list to append the new child to. Also it appears that you are not intending to have the children have children.
That being said it seems you may actually want to ask a different question, such as Composition vs Aggregation. There is such a design choice as Inheritance vs Composition which actually may be particularly interesting for Python, but it mainly asks whether you want to reuse code by copying the behavior of a standalone parent class (inheritance) or you want to separate different class behavior granules (for lack of better word) and then create classes which are compositions of these granules.
have a look at this! The book referenced is also well known and has a good catalogue for different design patterns.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With