python-code-standards

To configure Ruff and Pyright in pyproject.toml, you define canonical sections for linting and type-checking. This standardizes Python tooling configurations to reduce code quality drift and establishes a consistent format, lint, type, and test workflow.

The best way to standardize Python linting and type-checking is by applying a unified pyproject.toml configuration. This establishes canonical settings for Ruff and Pyright, along with taskipy task aliases and pre-commit hooks, to prevent inconsistent code quality.

You set up pre-commit hooks by defining their structure within your standardized pyproject.toml. This integrates Ruff linting and Pyright type-checking into your workflow, ensuring code quality is automatically validated before commits.

Yes, you can use different Ruff lint rules for tests by defining per-file ignores in your pyproject.toml. This allows you to enforce pydocstyle requirements globally while applying common ignore or override patterns specifically for test files.

No, it includes specific decision guidance to avoid overwriting team-owned tooling conventions in shared repositories. This helps you maintain a personal safety bar without disrupting established team configurations.

You run format, lint, type, and test workflows by applying the provided taskipy task aliases defined in your pyproject.toml. This creates a unified quality gate that sequences Ruff, Pyright, and pytest into a single automated command.