Skip to content
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.

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

[syntax-error] Detail the reason why pylint can't analyse the file after a syntax error #9589

Merged
merged 3 commits into from May 2, 2024

Conversation

Pierre-Sassoulas
Copy link
Member

Type of Changes

Type
βœ“ πŸ“œ Docs

Description

Closes #9588

@Pierre-Sassoulas Pierre-Sassoulas added Documentation πŸ“— Skip news πŸ”‡ This change does not require a changelog entry labels May 2, 2024
@Pierre-Sassoulas Pierre-Sassoulas changed the title Add details on syntax-errors [syntax-error] Detail the reason why pylint can't analyse the file after a syntax error May 2, 2024
Copy link

codecov bot commented May 2, 2024

Codecov Report

All modified and coverable lines are covered by tests βœ…

Project coverage is 95.81%. Comparing base (82ef647) to head (44dc449).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #9589   +/-   ##
=======================================
  Coverage   95.81%   95.81%           
=======================================
  Files         173      173           
  Lines       18825    18825           
=======================================
  Hits        18038    18038           
  Misses        787      787           

@Pierre-Sassoulas Pierre-Sassoulas merged commit a831422 into main May 2, 2024
26 checks passed
@Pierre-Sassoulas Pierre-Sassoulas deleted the Pierre-Sassoulas-patch-1 branch May 2, 2024 16:02
@mbyrnepr2
Copy link
Member

Thanks @Pierre-Sassoulas .Sorry for being tardy :) I see DaniΓ«l is on the ball (as they say).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation πŸ“— Skip news πŸ”‡ This change does not require a changelog entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Pylint gets stuck on syntax errors, any way to get the whole report even if there is syntax errors?
3 participants