Title: docs: operator dunder (`__add__`, et al.) invocations described incorrectly
Type: enhancement Stage: patch review
Components: Documentation Versions: Python 3.10, Python 3.9, Python 3.8, Python 3.7, Python 3.6
Status: open Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, wchargin
Priority: normal Keywords: patch

Created on 2020-09-03 20:30 by wchargin, last changed 2020-09-03 20:40 by wchargin.

Pull Requests
URL Status Linked Edit
PR 22084 open wchargin, 2020-09-03 20:40
Messages (1)
msg376316 - (view) Author: William Chargin (wchargin) * Date: 2020-09-03 20:30
The operator override dunder methods, like `__add__`, are described in
the “Data model” docs here:

Those docs say:

> For instance, to evaluate the expression `x + y`, where `x` is an
> instance of a class that has an `__add__()` method, `x.__add__(y)` is
> called.

But this is not correct: `x + y` always uses `type(x).__add__`, which
may be different from `x.__add__` if `__add__` has been set directly on
the instance.


class C:
    def __add__(self, other):
        return "from class"

c = C()
print(c + c)  # prints "from class"

c.__add__ = lambda other: "from instance"
print(c.__add__(c))  # prints "from instance"
print(type(c).__add__(c, c))  # prints "from class"

print(c + c)  # prints "from class"!

The same issue appears in the reversed operator dunder (`__radd__`,
et al.) docs below.

I have a patch that I can submit as a PR; just need a bpo number.
Date User Action Args
2020-09-03 20:40:56wcharginsetkeywords: + patch
stage: patch review
pull_requests: + pull_request21170
2020-09-03 20:30:50wchargincreate