chore(tooling)!: replace Black formatting with Ruff#146
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the context of this PR?
Replace Black with Ruff as the default Python formatter, reducing duplicated tooling and simplifying the generated project configuration.
Historically, Ruff did not fully cover Black’s formatting behaviour, including some handling of overlong lines. Ruff’s formatter is now mature enough to serve as the default for this template, and consolidating linting and formatting into a single tool simplifies dependency management, packaging, configuration, and maintenance.
This is a breaking change because generated projects no longer install or invoke Black. Existing projects, CI pipelines, local development workflows, and automation that rely on Black must migrate to ruff format.
Projects that require Black-specific formatting behaviour can still add Black alongside Ruff and configure their formatting commands accordingly.
How to review
Ensure the changes make sense
Follow-up Actions
List any follow-up actions (if applicable), like needed documentation updates or additional testing.