-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Pylint gets stuck on syntax errors, any way to get the whole report even if there is syntax errors? #9588
Labels
Comments
Alif829
added
Documentation 📗
Needs triage 📥
Just created, needs acknowledgment, triage, and proper labelling
Question
labels
May 2, 2024
Pierre-Sassoulas
removed
the
Needs triage 📥
Just created, needs acknowledgment, triage, and proper labelling
label
May 2, 2024
Pierre-Sassoulas
added a commit
that referenced
this issue
May 2, 2024
Thank you for opening the issue, could you review #9589 please ? :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Question
is there a way to get the whole issues of the code even with syntax errors? because currently, pylint gets stuck if it gets syntax error and flag only that syntax error issue not other issues even if they are available.
Documentation for future user
I expected this information to be in the configuration
Additional context
No response
The text was updated successfully, but these errors were encountered: