> No, it definitionally isn't. The entire point is that `+` is being used to represent operations where `+` makes intuitive sense. Huh? There's no restriction

> No, it definitionally isn't. The entire point is that `+` is being used to represent operations where `+` makes intuitive sense. Huh? There's no restriction in Python's type system that says `+` has to "make sense". import requests class Smoothie: def __init__(self, fruits): self.fruits = fruits def __repr__(self): return " and ".join(self.fruits) + " smoothie" class Fruit: def __init__(self, name): self._name = name def __add__(self, other): if isinstance(other, Fruit): return Smoothie([self._name, other._name]) return requests.get("https://google.com") if __name__ == "__main__": print(Fruit("banana") + Fruit("mango")) print(Fruit("banana") + 123) > banana and mango smoothie > <Response [200]> So we have Fruit + Fruit = Smoothie. Overly cute, but sensible from a CS101 OOP definition and potentially code someone might encounter in the real world, and demonstrates how not all T + T -> T. And we have Fruit + number = requests.Response. Complete nonsense, but totally valid in Python. If you're writing a generic method `slow_add` that needs to support `a + b` for any two types -- yes, you have to support this nonsense.