Skip to content

Adopt ruff (or other linter) #193

@alcides

Description

@alcides

Different contributors have different code styles. The recommended approach to handle this is to have a pre-commit/CI step that validates that the source code follows some style.

For Python, I have been using ruff, that automatically fixes many issues, and detects code smells.

If you think it's useful, I can prepare a PR. But I don't think I should spend the time if you do not think it's worthwhile.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions