David Peter 4ef2c223c9 [ty] Respect MRO_NO_OBJECT_FALLBACK policy when looking up symbols on type instances (#18312) ... ## Summary This should address a problem that came up while working on https://github.com/astral-sh/ruff/pull/18280. When looking up an attribute (typically a dunder method) with the `MRO_NO_OBJECT_FALLBACK` policy, the attribute is first looked up on the meta type. If the meta type happens to be `type`, we go through the following branch in `find_name_in_mro_with_policy`: 97ff015c88/crates/ty_python_semantic/src/types.rs (L2565-L2573) The problem is that we now look up the attribute on `object` *directly* (instead of just having `object` in the MRO). In this case, `MRO_NO_OBJECT_FALLBACK` has no effect in `class_member_from_mro`: c3feb8ce27/crates/ty_python_semantic/src/types/class.rs (L1081-L1082) So instead, we need to explicitly respect the `MRO_NO_OBJECT_FALLBACK` policy here by returning `Symbol::Unbound`. ## Test Plan Added new Markdown tests that explain the ecosystem changes that we observe.		2025-05-26 12:03:29 +02:00
..
resources	[ty] Respect MRO_NO_OBJECT_FALLBACK policy when looking up symbols on type instances (#18312)	2025-05-26 12:03:29 +02:00
src	[ty] Respect MRO_NO_OBJECT_FALLBACK policy when looking up symbols on type instances (#18312)	2025-05-26 12:03:29 +02:00
tests	Switch to Rust 2024 edition (#18129)	2025-05-16 13:25:28 +02:00
build.rs	Rename Red Knot (#17820)	2025-05-03 19:49:15 +02:00
Cargo.toml	Rename Red Knot (#17820)	2025-05-03 19:49:15 +02:00
mdtest.py	Rename Red Knot (#17820)	2025-05-03 19:49:15 +02:00
mdtest.py.lock	Rename Red Knot (#17820)	2025-05-03 19:49:15 +02:00