ruff/crates/ty_python_semantic/resources/mdtest/call at 43eddc566faffd50da7b1e9b71a2c63f02ab31d8 - ruff

mirror of https://github.com/astral-sh/ruff synced 2026-01-24 23:10:51 -05:00

Files

David Peter 6341bb7403 [ty] Treat Callable dunder members as bound method descriptors (#20860 )

## Summary

Dunder methods (at least the ones defined in the standard library)
always take an instance of the class as the first parameter. So it seems
reasonable to generally treat them as bound method descriptors if they
are defined via a `Callable` type.

This removes just a few false positives from the ecosystem, but solves
three user-reported issues:

closes https://github.com/astral-sh/ty/issues/908
closes https://github.com/astral-sh/ty/issues/1143
closes https://github.com/astral-sh/ty/issues/1209

In addition to the change here, I also considered [making `ClassVar`s
bound method descriptors](https://github.com/astral-sh/ruff/pull/20861).
However, there was zero ecosystem impact. So I think we can also close
https://github.com/astral-sh/ty/issues/491 with this PR.

closes https://github.com/astral-sh/ty/issues/491

## Test Plan

Added regression test

2025-10-14 14:27:52 +02:00

annotation.md

ty_python_semantic: add union type context to function call type errors

2025-05-09 13:40:51 -04:00

builtins.md

[ty] More precise type inference for dictionary literals (#20523 )

2025-09-24 18:12:00 -04:00

callable_instance.md

[ty] Rename "possibly unbound" diagnostics to "possibly missing" (#20492 )

2025-09-23 14:26:55 +00:00

callables_as_descriptors.md

[ty] Treat Callable dunder members as bound method descriptors (#20860 )