Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Work when pylint is called pylint-script.py #13

Closed
dmnd opened this issue Jul 29, 2014 · 1 comment
Closed

Work when pylint is called pylint-script.py #13

dmnd opened this issue Jul 29, 2014 · 1 comment

Comments

@dmnd
Copy link
Member

dmnd commented Jul 29, 2014

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 of pylint.

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, then pylint-script.py, then prompting the user to enter the path in config.

@florianb
Copy link
Contributor

@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.

@fnkr fnkr mentioned this issue Oct 10, 2014
@dmnd dmnd closed this as completed in ae8b73d Dec 1, 2014
dmnd added a commit that referenced this issue Dec 1, 2014
Update regex to support pylint-script.py

Fixes #13.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants