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

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

Closed
Alif829 opened this issue May 2, 2024 · 1 comment · Fixed by #9589

Comments

@Alif829
Copy link

Alif829 commented May 2, 2024

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

@Alif829 Alif829 added Documentation 📗 Needs triage 📥 Just created, needs acknowledgment, triage, and proper labelling Question labels May 2, 2024
@Pierre-Sassoulas Pierre-Sassoulas removed the Needs triage 📥 Just created, needs acknowledgment, triage, and proper labelling label May 2, 2024
@Pierre-Sassoulas Pierre-Sassoulas self-assigned this May 2, 2024
Pierre-Sassoulas added a commit that referenced this issue May 2, 2024
@Pierre-Sassoulas
Copy link
Member

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
Projects
None yet
2 participants