Python 3.7 debugger does not launch (but Python 2.7 works)

[jdwestwood]

VSCode version 1.39.1
Python 2019.10.41019
Windows 10 Home with Python 3.7.1 and 2.7.15 installed

Steps to reproduce:
Create a workspace folder with:

1. settings.json:

{
    // Python 3.7.1
    "python.pythonPath": "C:\\Python37\\python.exe"
}

2. launch.json:

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
        },
    ]
}

3. test.py:

hello = "Hello"
print(hello)

Debug test.py using Python: Current File.

Expected result:
Program runs in the integrated terminal and prints "Hello".

Actual result:
Program does not run.

"Python" terminal output (pylint output removed):

User belongs to experiment group 'ShowPlayIcon - start'
User belongs to experiment group 'ShowExtensionSurveyPrompt - control'
User belongs to experiment group 'DebugAdapterFactory - experiment'
User belongs to experiment group 'PtvsdWheels37 - experiment'
Starting Microsoft Python language server.
> conda --version
> pyenv root
> python3.7 -c "import sys;print(sys.executable)"
> python3.6 -c "import sys;print(sys.executable)"
> python3 -c "import sys;print(sys.executable)"
> python2 -c "import sys;print(sys.executable)"
> python -c "import sys;print(sys.executable)"
> py -3.7 -c "import sys;print(sys.executable)"
> py -3 -c "import sys;print(sys.executable)"
> py -2 -c "import sys;print(sys.executable)"
> py -3.6 -c "import sys;print(sys.executable)"
> C:\Python37\python.exe -c "import sys;print(sys.executable)"
> conda info --json
> ~\AppData\Local\Microsoft\WindowsApps\python.exe c:\Users\John\.vscode\extensions\ms-python.python-2019.10.41019\pythonFiles\interpreterInfo.py
> ~\AppData\Local\Microsoft\WindowsApps\python.exe c:\Users\John\.vscode\extensions\ms-python.python-2019.10.41019\pythonFiles\interpreterInfo.py
> ~\AppData\Local\Microsoft\WindowsApps\python3.exe c:\Users\John\.vscode\extensions\ms-python.python-2019.10.41019\pythonFiles\interpreterInfo.py
> ~\AppData\Local\Microsoft\WindowsApps\python3.exe c:\Users\John\.vscode\extensions\ms-python.python-2019.10.41019\pythonFiles\interpreterInfo.py

> C:\Python37\python.exe c:\Users\John\.vscode\extensions\ms-python.python-2019.10.41019\pythonFiles\ptvsd_folder_name.py
> C:\Python37\python.exe c:\Users\John\.vscode\extensions\ms-python.python-2019.10.41019\pythonFiles\ptvsd_folder_name.py

Additional info:
When the Python 2.7.15 interpreter is specified for python.pythonPath, everything works as expected: test.py runs and breakpoints are hit.

[olegpts]

here is the solution/wa
microsoft/vscode-python#7836

"For anyone looking, the workaround is to add requirements.txt file with this content:

jedi==0.15.1
parso==0.5.1
isort==4.3.21
ptvsd==5.0.0a5
pyparsing==2.4.0
six==1.12.0
packaging==19.2

to this location on windows:
%USERPROFILE%/.vscode\extensions\ms-python.python-2019.10.41019\

or this location on Linux/Mac:
$HOME/.vscode/extensions/ms-python.python-2019.10.41019/
"

[vscodebot]

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines.

Happy Coding!