Debugging a script run from within a virtual environment's directory does not work

Environment data

• VS Code version: 1.27.1
• Extension version (available under the Extensions sidebar): Python 2018.8.0
• OS and version: macOS HighSierra 10.13.6
• Python version (& distribution if applicable, e.g. Anaconda): Python 3.7.0
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): venv
• Relevant/affected Python packages and their versions: XXX

Actual behavior

When I set a breakpoint in the venv environment, and click the debug, the runpy.py file popped up and the program stopped at line 85.

Expected behavior

The program should have stopped at the line where I set the breakpoint.

Steps to reproduce:

1. python3 -m venv test
2. Open the test folder and change the workspace settings "python.pythonPath": "${workspaceFolder}/bin/python3"
3. Then try to write some python code, for example,

a = 1
b = 2

print(a+b)

set a breakpoint at line 2, click the debug, a runpy.py file popped up and the program stops at line 85: exec(code, run_globals), as the following image shows.

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Nothing

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

The following statements are executed in the integrated terminal :

[reyshawn:~/Desktop/test]$ cd /Users/reyshawn/Desktop/test ; env "PYTHONIOENCODING=UTF-8" "PYTHONUNBUFFERED=1" "PYTHONPATH=/Users/reyshawn/.vscode/extensions/ms-python.python-2018.8.0/pythonFiles/experimental/ptvsd" /Users/reyshawn/Desktop/test/bin/python3 -m ptvsd --host localhost --port 49846 /Users/reyshawn/Desktop/test/a.py

launch.json:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Current File (Integrated Terminal)",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal"
        },
        {
            "name": "Python: Attach",
            "type": "python",
            "request": "attach",
            "port": 5678,
            "host": "localhost"
        },
        {
            "name": "Python: Django",
            "type": "python",
            "request": "launch",
            "program": "${workspaceFolder}/manage.py",
            "console": "integratedTerminal",
            "args": [
                "runserver",
                "--noreload",
                "--nothreading"
            ],
            "django": true
        },
        {
            "name": "Python: Flask",
            "type": "python",
            "request": "launch",
            "module": "flask",
            "env": {
                "FLASK_APP": "app.py"
            },
            "args": [
                "run",
                "--no-debugger",
                "--no-reload"
            ],
            "jinja": true
        },
        {
            "name": "Python: Current File (External Terminal)",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "externalTerminal"
        }
    ]
}

[brettcannon]

To debug into third-party code (which is anything inside a venv), set "debugStdlib": true in your launch.json. We are going to be getting a better name and improving the support in #2087.

[OliveIT]

I faced the same issue. Any updates?