Dylan 965a4dd731 [isort] Check full module path against project root(s) when categorizing first-party (#16565) ...

When attempting to determine whether `import foo.bar.baz` is a known
first-party import relative to [user-provided source
paths](https://docs.astral.sh/ruff/settings/#src), when `preview` is
enabled we now check that `SRC/foo/bar/baz` is a directory or
`SRC/foo/bar/baz.py` or `SRC/foo/bar/baz.pyi` exist.

Previously, we just checked the analogous thing for `SRC/foo`, but this
can be misleading in situations with disjoint namespace packages that
share a common base name (e.g. we may be working inside the namespace
package `foo.buzz` and importing `foo.bar` from elsewhere).

Supersedes #12987 
Closes #12984

2025-05-05 11:40:01 -05:00

..

resources/test/fixtures/cfg

Control flow: return and raise (#17121)

2025-04-03 08:30:29 -05:00

src

[isort] Check full module path against project root(s) when categorizing first-party (#16565)

2025-05-05 11:40:01 -05:00

Cargo.toml

Control flow graph: setup (#17064)

2025-04-01 05:53:42 -05:00