Python Code Style

Use tools for mechanical style and human judgment for names, boundaries, and documentation. The goal is readable code that is easy to review and maintain.

For concrete config and docstring templates, read references/style-configs.md.

Defaults

• Use ruff for linting/import sorting/formatting unless the project already has a different standard.
• Use type hints for public APIs and non-obvious internal boundaries.
• Prefer clear names over abbreviations.
• Keep imports grouped: standard library, third-party, local.
• Let the formatter decide line wrapping.

Review Checklist