Skip to content

fix: resolve pylint config errors breaking super-linter #433

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zkoppert merged 1 commit into from
Feb 27, 2026
Merged

fix: resolve pylint config errors breaking super-linter #433

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions .github/linters/.python-lint
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,10 +99,6 @@ recursive=no
# source root.
source-roots=

# When enabled, pylint would attempt to guess common misconfiguration and emit
# user-friendly hints instead of false-positive error messages.
suggestion-mode=yes

# Allow loading of arbitrary C extensions. Extensions are imported into the
# active Python interpreter and may run arbitrary code.
unsafe-load-any-extension=no
Comment on lines 100 to 104

Copilot AI Feb 25, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR description says too-many-nested-blocks was added to the pylint disable= list, but this change isn’t present in .github/linters/.python-lint (and too-many-nested-blocks doesn’t appear anywhere in this config). Please either add it to the disable= list under [MESSAGES CONTROL] (if it’s still needed to unblock CI) or update the PR description to match the actual change set.

Copilot uses AI. Check for mistakes.
Expand Down
Loading