Kevin Millikin

I have a different view: we *should* specify this behavior (currently `Function.apply`) in the spec. That allows implementations to reason about it and optimize it other than just calling a...

@lrhn That's the issue. Accessibility is explicit in the definition of inheritance in 10.9.1. > Let C be a class, let A be a superclass of C, and let S1...

I think using the "current library" (defined as the library currently being compiled) in method lookup is intended to take care of that case. In the implementation of `foo` the...

Declarations could also be `final` or `const`. I can't immediately think of a way that it could be observed, but we should say whether they are fresh variables per iteration...

The PEP is not as clear as it could be. The phrase "takes on the type" is used informally and never defined in the PEP. It might mean that it...

> The `issubclass` logic in pyright and mypy make use of an "anonymous subclass" that derives from two base classes. I guess you could call this a rudimentary intersection, but...

> You're arguing that the narrowed type should be `List[object] & List[str]` (i.e. an intersection between the input type and the type guard type) rather than `List[str]`. Just to clarify...

I think "might plausibly be" was part of my informal intuition behind the rules. The rules themselves are intended to define the relation.