Anaconda Python not recognized - "Failed to launch the Python Process"

[srijansood]

Environment data

VS Code version: 1.18.1
Python Extension version: 0.8.0
Python Version: Python 3.6.3 :: Anaconda, Inc.
OS and version: Windows 10 v1709, conda installed in WSL Ubuntu

Actual behavior

• Intelisense/Autocomplete do not work
• Launching debug (F5) on a python file:
  • Error Failed to launch the Python Process, please validate the path /home/srijan/anaconda3/bin/python.
  • Debug Console: Error: spawn /home/srijan/anaconda3/bin/python ENOENT
• Ctrl-Shift-P > Python: Select Interpreter says current: /home/srijan/anaconda3/bin/python...There are no entries to pick from.

Expected behavior

Anaconda Python should work with VS Code from what I understand.

• Possibly related to No option to select Anaconda root #22

Steps to reproduce:

• Launch VSCode
• Set "python.pythonPath": "/home/<user>/anaconda3/bin/python"
• Try Autocomplete or Debugging a file

Logs

Output from Python output panel

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

spawn ctags ENOENT: Error: spawn ctags ENOENT
	at exports._errnoException (util.js:1050:11)
	at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
	at onErrorNT (internal/child_process.js:367:16)
	at _combinedTickCallback (internal/process/next_tick.js:80:11)
	at process._tickCallback (internal/process/next_tick.js:104:9)

Failed to launch the Python Process, please validate the path '/home/srijan/anaconda3/bin/python'

[DonJayamanne]

1. Please could you type the following command in the terminal window and let me know what you get:

/home/srijan/anaconda3/bin/python

[srijansood]

It launches the Python shell.

Python 3.6.3 |Anaconda, Inc.| (default, Oct 13 2017, 12:02:49)
[GCC 7.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>

[DonJayamanne]

@srijansood
Please could you also provide the contents of the following files:

• .vscode/launch.json
• .vscode/settings.json

[DonJayamanne]

@srijansood Please ignore the above queries.
I'm closing this issue in favor of #67
Currently the extension does not support WSL.