[issue25432] isinstance documentation doesn't explain what happens when type is tuple

Georg Brandl added the comment: But without using the word "disjunctive". -- nosy: +georg.brandl ___ Python tracker ___ ___ Python-bug

[issue25432] isinstance documentation doesn't explain what happens when type is tuple

eryksun added the comment: Since Python has multiple inheritance, it could be misconstrued as a conjunctive test. For example, if c is an instance of C, which subclasses both A and B, then someone might think isinstance(c, (A, B)) requires c to be an instance of both A and B. The description c

[issue25432] isinstance documentation doesn't explain what happens when type is tuple

R. David Murray added the comment: I don't see any ambiguity here. There are other Python APIs with the same behavior, and all we say is that it can be a tuple (eg: str.startswith). That is, I don't see any other way a tuple could be interpreted that would make any sense. -- nosy: +

[issue25432] isinstance documentation doesn't explain what happens when type is tuple

New submission from Michael Crouch: In the section on isinstance() in the Python Standard Library documentation Chapter 2 (https://docs.python.org/3.6/library/functions.html#isinstance) , it says that classinfo "may be a tuple of type objects", but it doesn't explain what the semantics are in