pylint not found even so it's in path from where VSCode was launched

[michaelaye]

Environment data

VS Code version: 1.19.3
Python Extension version: 2018.1.0
Python Version: Python 3.6.4 | packaged by conda-forge | (default, Dec 23 2017, 16:54:01)
[GCC 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
OS and version: macOS 10.12.6

Actual behavior

Opening a Python repo for the first time, I get pop-up that pylint is not installed.

Expected behavior

pylint is in the path where I launched vscode, it should find it:
(stable) └─❱❱❱ which pylint +7540 12:53 ❰─┘
/Users/klay6683/miniconda3/envs/stable/bin/pylint

Steps to reproduce:

• Open a folder with a Python package

Logs

Output from Python output panel

##########Linting Output - pylint##########

Linter 'pylint' is not installed. Please install it or select another linter".
Error: Module 'pylint' not installed.

Note, I also noticed that in the terminal that I can open my conda env is not activated, even after typing conda activate stable in there.
Is that maybe a problem with the new conda 4.4.x, which changed for conda to be a script instead of a python executable?

(yes, I'm running zsh, but everything works in my iTerm2 terminal).

Output from Console window (Help->Developer Tools menu)

[michaelaye]

Ok, so the pylint errors go away when I manually select my Python interpreter to be my Anaconda env. If that's by design, we can close this issue.
Interestingly, even after that the inbuilt terminal does not point to it though, so I can't launch an ipython in the terminal, even after selecting my correct conda env.

[DonJayamanne]

manually select my Python interpreter to be my Anaconda env. If that's by design, we can close this issue.

yes, thats the expected behavior.

Interestingly, even after that the inbuilt terminal does not point to it though, so I can't launch an

Please use the command Python: Create Terminal. This will create a terminal with the necessary Python environment activated. Using the standard approach will merely create a terminal but without activating the environment.

[michaelaye]

Please use the command Python: Create Terminal. This will create a terminal with the necessary Python environment activated. Using the standard approach will merely create a terminal but without activating the environment.

This does not work with conda 4.4.x:

source activate stable

┌─( ~/D/s/planetpy λ:master | ✱ ◼ 3ebce8e )────────────────────────────────────────────────────────────────────( @MacL2938 )─┐
└─❱❱❱ source activate stable                                                                                   +7509 13:55 ❰─┘
source: no such file or directory: activate

even so the conda people said things should stay backwards compatible.

[DonJayamanne]

@michaelaye Please could you create a separate issue for that. Thanks
Looks like the conda environment is not detect.