Pre Commit Linter Failing for python_utils
See original GitHub issueDescribe the bug
While running pre_commit_linter.py
for just python_utils.py
it fails with the error AttributeError: 'list' object has no attribute 'trimmed_messages'
To Reproduce Steps to reproduce the behavior:
- Run the command
python -m scripts.linters.pre_commit_linter --files python_utils.py
Observed behavior
An error is thrown
AttributeError: 'list' object has no attribute 'trimmed_messages'
Expected behavior It should run without errors
Screenshots
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
hooks: pylint: pre-commit failure #4145 - iterative/dvc - GitHub
pre -commit-config.yaml states that the pylint hook is defined locally, yet .pre-commit-hooks.yaml fails to define it.
Read more >pylint precommit - only fail on specific categories (errors/fatals ...
My objective: I want pylint (in combination with pre-commit hooks) not to fail with warnings of the category C,R,W, but on E,F (Errors...
Read more >Running Python Linters with Pre-commit Hooks
Pre -commit hooks can be a neat way to run automated ad-hoc tasks before submitting a new git commit. These tasks may include...
Read more >Supported hooks - pre-commit
cheetah-reorder-imports - This hook reorders imports in cheetah files. cheetah-flake - Lint cheetah code using flake8 and some other checks.
Read more >Stop your builds failing with git pre commit hooks | PreviousNext
Depending on how the build is configured, failing coding standards can result in the entire build failing. Because linting is generally not ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @SanjaySajuJacob Thanks for looking into this, it looks like the function is removed now after the py3 migration. I agree that this issue can be closed now!
Hi @aasiffaizal, I tried replicating the behavior described by the issue by running
python -m scripts.linters.pre_commit_linter --files core/python_utils.py
and it seems to have passed all checks. Since this issue does not occur anymore, can it be closed? Thanks