-
Notifications
You must be signed in to change notification settings - Fork 285
Allow usage of Pylint via stdin #831
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
Conversation
159a7b8
to
5a2c8df
Compare
This closes #796 |
@ccordoba12 @goanpeca Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay, I ran it locally and gave it a quick review. All checks out.
Thanks @mpanarin !
Mimics flake8 stdin usage. This makes it possible for pylint to run on unsaved files works on pylint>=2.5.0 I didn't notice a performance degradation in terms of running pylint itself. Of course, there *is* a performance hit overall, as pylint will be run on every change, and it can be fairly slow
5a2c8df
to
bd1df91
Compare
Can this be merged? It's been 2 month already ( |
We need to merge first #842 to verify that tests pass in this PR before merging. |
Mimics
flake8
stdin usage.This makes it possible for pylint to run on unsaved files
works on
pylint>=2.5.0
and python 3+I didn't notice a performance degradation in terms of running pylint itself.
Of course, there is a performance hit overall, as pylint will be run on every
change, and it can be fairly slow but there was a bunch of requests for that in emacs-lsp
community.
Disabled by default
ex. @chama-chomo
Fixes #796