astral-sh/ruff - CodSpeed

ruff

Blog Docs Changelog

Performance History

Latest Results

[flake8-bugbear] Fix nested-loop and branch-tracking correctness

anishgirianish:fix/b909-break-continue-branch-tracking

4 hours ago

[ty] Implement unwrap_block refactor code action Example --- ```text info[code-action(refactor)]: Unwrap this statements block --> main.py:3:12 | 2 | if 1: 3 | if True: | ^ 4 | foo 5 | bar() | 1 | 2 | if 1: - if True: - foo - bar() - if 1: - baz - xxx - ... 3 + foo 4 + bar() 5 + if 1: 6 + baz 7 + xxx 8 + ... 9 | ... ```

A4-Tacks:unwrap-block-action

5 hours ago

charlie/td-narrow

7 hours ago

[formatter] Fix CI: update snapshot and use legacy key for uv backend - Update `all_rules_default_options` snapshot to match the new COM812 warning message text (raw string literal for embedded quotes) - Use legacy `skip-magic-trailing-comma` key in the uv backend for compatibility with external `uv format` builds that don't yet recognize the new `magic-trailing-comma` setting

XuehaiPan:magic-trailing-comma-normalize

7 hours ago

[ty] Improve `type=` mixin support for functional `Enum(...)` (#24571) ## Summary We now return `Unknown` for members in cases in which a `type=` mixin is used with explicit values, like: ```python E = Enum("E", {"A": "1", "B": 1}, type=int) ``` Since in this case, `B` would actually be an alias of `A`. If it's a non-explicit form (like `Enum("E", "A B", type=str)`), we return values of the provided `type` (but not literals), with known members. We could probably do a better job with the values in some of these cases, but it doesn't seem worth it to me right now. If the `type=` is incompatible with the enum base (e.g., `BadIntEnum = IntEnum("BadIntEnum", "RED", type=str)`), we also throw an error.

main

7 hours ago

Update ecosystem-analyzer pins (#24573) Co-authored-by: Claude <noreply@anthropic.com>

main

8 hours ago

[formatter] Add `magic-trailing-comma` option with `normalize` mode to make formatter COM-safe Add a new `magic-trailing-comma` string enum option (`"respect"` | `"ignore"` | `"normalize"`) to replace the deprecated boolean `skip-magic-trailing-comma`. The `"normalize"` mode makes the formatter COM-safe — `COM812` and the formatter converge to the same output in a single pass by: - Ignoring existing trailing commas as expansion signals (like `"ignore"`) - Eliminating the compact multi-line layout for function calls/defs, ensuring every multi-line expression is one-per-line with a trailing comma — including single-argument calls forced open by comments - Removing unnecessary trailing commas from single-line expressions This resolves the long-standing formatter/linter oscillation where `COM812` adds trailing commas that the formatter then re-expands.

XuehaiPan:magic-trailing-comma-normalize

8 hours ago

Review feedback

charlie/td-narrow

8 hours ago

Latest Branches

0%

[flake8-bugbear] Fix break/continue handling in loop-iterator-mutation#24440

4 hours ago

1a82157

anishgirianish:fix/b909-break-continue-branch-tracking

0%

[ty] Implement unwrap_block refactor code action#24574

7 hours ago

36a228c

A4-Tacks:unwrap-block-action

0%

[ty] Narrow TypedDicts through `isinstance(..., dict)`#23946

7 hours ago

a91ccd3

charlie/td-narrow

© 2026 CodSpeed Technology

Home Terms Privacy Docs