Ruff best practices

Use when linting or formatting Python code with Ruff, configuring pyproject.toml / ruff.toml, or consolidating older Python tooling around the Ruff CLI.

Mental model

• Treat Ruff as a unified Python quality tool: linter first, formatter when adopted, and optionally language server support in editors.
• Prefer one shared Ruff configuration for the repo instead of separate local conventions in editors, pre-commit hooks, and CI.
• Adopt rules deliberately. Fast execution is not a reason to enable a noisy ruleset without a rollout plan.

Configuration

• Configure Ruff in pyproject.toml, ruff.toml, or .ruff.toml and keep the repo explicit about which file owns policy.
• Keep [tool.ruff] for shared settings such as line length, target version, include/exclude behavior, and cache-aware file boundaries.
• Put lint-specific settings under [tool.ruff.lint] and formatter-specific settings under [tool.ruff.format].

Linting