What the developer wrote
Authored by Ioan Bizău
chore: tighten pylint
[no changelog]
What changed, and why it matters
This commit only changes the project's Python linter configuration file (.pylintrc) to enable two additional code-quality checks: 'pointless-exception-statement' and 'pointless-statement'. These checks flag code that has no effect, such as an expression or exception object written on its own line without being raised or used. There is no change to the firmware source code, runtime behavior, or any security-sensitive logic. It is a routine tooling/development hygiene change.
No security action required. Treat as a normal development tooling change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds two lint rules to .pylintrc: pointless-exception-statement and pointless-statement. These are static-analysis rules in pylint that warn when an expression statement has no side effects (e.g., writing ‘Exception()’ without ‘raise’, or a bare expression whose result is discarded). The change affects only CI/static-analysis behavior, not compiled firmware or host tooling binaries. No source files were modified.
Changed components
.pylintrc (pylint configuration)Inspect captured patch +2 / −0
diff --git a/.pylintrc b/.pylintrc
index 0963d3e31..94a3328fc 100644
--- a/.pylintrc
+++ b/.pylintrc
@@ -27,6 +27,8 @@ enable=
inconsistent-return-statements,
lost-exception,
pointless-string-statement,
+ pointless-exception-statement,
+ pointless-statement,
simplifiable-if-statement,
super-init-not-called,
superfluous-parens,
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.