Install debugger to work with extension when running from source

[karthiknadig]

Currently if you build and debug the extension from source, you won;t have ptvsd installed in the extension directory (which is the directory you git check out). The extension will look for the debugger under that directory. Since it is not installed there it will fail to run.

Workaround:

Suppose you have extension code checked out in this location: C:\GIT\vscode-python, then Run these two commands. You will need both.

Install without wheels:

python -m pip --disable-pip-version-check install -t C:\GIT\vscode-python\pythonFiles\lib\python\new_ptvsd\no_wheels --no-cache-dir --implementation py --no-deps --upgrade ptvsd==5.0.0a8

Install with wheels:

python -m pip --disable-pip-version-check install -t C:\GIT\vscode-python\pythonFiles\lib\python\new_ptvsd\wheels --no-cache-dir --no-deps --upgrade  ptvsd==5.0.0a8

[karrtikr]

The commands you mentioned seems incomplete. It's missing what to install (ptvsd).

[karthiknadig]

@karrtikr Ah. Updated the commands. sorry.

[DonJayamanne]

This used to be possible via the gulp command installPythonLibs.
I think it was removed, hence IMHO its a regression.

Please note, you have the exact same issue with Jedi, Sorting Imports and the like. I.e. there are other Python libraries required for running from source.
Hence it should all be done the same way (one line command, & preferably something available easily from VS Code tasks or similar - yes I'm leaning towards gulp, as thats easy for CLI and VS Code task integration).