Explicitly ignore existing linter violations - #1206
Merged
Merged
Conversation
mxsrc
force-pushed
the
explicit-linter-ignores
branch
from
August 1, 2026 17:40
0b489b5 to
9f56f49
Compare
More recent linter versions support more checks and enable them by default. Generally, we should try to adopt them to arrive at a more cherent codebase. Instead of pinning an old ruff version, this explicitly disables all checks that we fail at present. We should try and remove the violations and enable the checks successively. For those checks that we simply do not agree with, we can document explicit exceptions.
mxsrc
force-pushed
the
explicit-linter-ignores
branch
from
August 1, 2026 17:41
9f56f49 to
0968894
Compare
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
1 participant
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.
More recent linter versions support more checks and enable them by default. Generally, we should try to adopt them to arrive at a more cherent codebase. Instead of pinning an old ruff version, this explicitly disables all checks that we fail at present. We should try and remove the violations and enable the checks successively. For those checks that we simply do not agree with, we can document explicit exceptions.