Skip to content

Make specific Black version a test dependency, enforce with GitHub actions #119

@toolness

Description

@toolness

The contribution documentation mentions that the codebase uses Black, but it doesn't mention what version... I know that Prettier (which I'm more familiar with) recommends pinning to a particular version, since its (rather opinionated) formatting can change from one version to the next... is Black the same, or are its formatting guidelines more set-in-stone?

Anyhow, I thought that it would also be nice to run black --check, either as part of the test.yml GitHub workflow or wrapped in a pytest test. That way you'd be able to tell if new PRs are using proper formatting.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ciContinuous integration with GitHub Actions

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions