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
the manual path selection doesnt appear to work, and I'm not seeing any sort of debug infos on why. I turned on the "force" option, "debug" option, and closing-and-reopening atom. I also tried with the "pylint" option turned on and off to see if anything different happened.
could this because apm is reporting 2.7.15+, but pylint was installed with pip3? that is; pip3 install pylama pylama-pylint pylint along with apm install linter-python.
also, is automatic pylama detection possible? I'm using the location provided by which:
> which pylama
/home/alligator/.local/bin/pylama
thanks!
edit: also note that one of the most common ways for using python3 as default is to add an alias, alias python=python3, however atom doesnt utilize the python command so even though I am using that alias, apm --version will still report the above. just noting for anyone else who has the same setup.
> python --version
Python 3.6.7
The text was updated successfully, but these errors were encountered:
the manual path selection doesnt appear to work, and I'm not seeing any sort of debug infos on why. I turned on the "force" option, "debug" option, and closing-and-reopening atom. I also tried with the "pylint" option turned on and off to see if anything different happened.
could this because
apm
is reporting2.7.15+
, butpylint
was installed withpip3
? that is;pip3 install pylama pylama-pylint pylint
along withapm install linter-python
.also, is automatic
pylama
detection possible? I'm using the location provided bywhich
:thanks!
edit: also note that one of the most common ways for using python3 as default is to add an alias,
alias python=python3
, however atom doesnt utilize thepython
command so even though I am using that alias,apm --version
will still report the above. just noting for anyone else who has the same setup.The text was updated successfully, but these errors were encountered: