You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
@dmnd great finding 👍 - there's an easy way to fix that. We'll let the initializer execute two calls, one for pylintand one for pylint-script. This call might then be recognized by the executionCheckHandlerwhich enables the linting for the correct command.
In #2 a lot of Windows users are having trouble with the
pylint
executable having an unexpected name.Changing:
versionRegEx = /pylint ([\d.]+)\,/
To:
versionRegEx = /pylint-script.py ([\d.]+)\,/
makes things work. Apparently some installations of pylint have a different executable name:
pylint-script.py
instead ofpylint
.We could fix this by copying what
linter-pep8
does: make the executable path a config option.An improvement on that could be trying
pylint
, thenpylint-script.py
, then prompting the user to enter the path in config.The text was updated successfully, but these errors were encountered: