astral-sh/ruff - CodSpeed

ruff

Blog Docs Changelog

Performance History

Latest Results

Merge branch 'main' into dcreager/breakest-the-cycle

dcreager/breakest-the-cycle

43 minutes ago

[ty] Handle `Definition`s in `SemanticModel::scope` (#21919)

main

57 minutes ago

micha/model-scope-definitions

58 minutes ago

[ty] Attach salsa db when running ide tests for easier debugging (#21917)

main

58 minutes ago

[ty] Don't show hover for expressions with no inferred type (#21924)

main

1 hour ago

[ty] Support `__all__ += submodule.__all__` ... and also `__all__.extend(submodule.__all__)`. I originally left out support for this since I was unclear on whether we'd really need it. But it turns out this is used somewhat frequently. For example, in `numpy`. See the comments on the new `Imports` type for how we approach this.

ag/support-all-submodule-extend

1 hour ago

[ty] avoid unions of generic aliases of the same class in fixpoint (#21909) Partially addresses https://github.com/astral-sh/ty/issues/1732 Fixes https://github.com/astral-sh/ty/issues/1800 ## Summary At each fixpoint iteration, we union the "previous" and "current" iteration types, to ensure that the type can only widen at each iteration. This prevents oscillation and ensures convergence. But some unions triggered by this behavior (in particular, unions of differently-specialized generic-aliases of the same class) never simplify, and cause spurious errors. Since we haven't seen examples of oscillating types involving class-literal or generic-alias types, just don't union those. There may be more thorough/principled ways to avoid undesirable unions in fixpoint iteration, but this narrow change seems like it results in strict improvement. ## Test Plan Removes two false positive `unsupported-class-base` in mdtests, and several in the ecosystem, without causing other regression.

main

1 hour ago

[ty] Squash false positive logs for failing to find `builtins` as a real module I recently started noticing this showing up in the logs for every scope based completion request: ``` 2025-12-11 11:25:35.704329935 DEBUG request{id=29 method="textDocument/completion"}:map_stub_definition: Module `builtins` not found while looking in parent dirs ``` And in particular, it was repeated several times. This was confusing to me because, well, of course `builtins` should resolve. This particular code path comes from looking for the docstrings of completion items. This involves a spelunking that ultimately tries to resolve a "real" module if the stub doesn't have available docstrings. But I guess there is no "real" `builtins` module, so `resolve_real_module` fails. Which is fine, but the noisy logs were annoying since this is an expected case. So here, we carve out a short circuit for `builtins` and also improve the log message.

main

1 hour ago

Active Branches

[ty] Defer all parameter and return type annotations

last run

43 minutes ago

+6%

[ty] Support `__all__ += submodule.__all__` in auto-import

last run

1 hour ago

0%

[ty] Move pytest search-path handling to desperate resolution

last run

2 hours ago

-1%

© 2025 CodSpeed Technology

Home Terms Privacy Docs