Python debugging not working after 2019.1.0 update with stopOnEntry=true

[tchapin]

Environment data

• VS Code version: 1.30.2
• Extension version (available under the Extensions sidebar): 2019.1.0
• OS and version: Windows 10 64-bit
• Python version (& distribution if applicable, e.g. Anaconda): 2.7 and 3.6.6
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda

Expected behaviour

Pressing run (F5) from the debug toolbar runs the script.

Actual behaviour

Pressing run (F5) from the debug toolbar does nothing.

Steps to reproduce:

1. setup a launch config using pythonPath to point to the python.exe to use
2. set python.pythonPath in workspace settings to point to the same python.exe
3. run a script

Logs

no output

[tchapin]

Reverting back to 2018.12.1 works like normal.

[DonJayamanne]

@tchapin Are you also using pipenv?
@bcxpro The issue you are experiencing is a dup of #4203

[tchapin]

@DonJayamanne No, not using pipenv

[ericsnowcurrently]

@tchapin, does anything get run in the terminal ("Python Debug Console")? Please paste your launch config and your settings.

[tchapin]

@ericsnowcurrently There is no output to the debug console. The run button seemingly does nothing.
Launch Config:

{
    // 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 2.7 (10.6)",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "pythonPath": "C:\\Python27\\ArcGIS10.6\\python.exe",
            "stopOnEntry": true,
            "console": "none"
        },
    ]
}

User Settings:

{
   // Whether to lint Python files.
  "python.linting.enabled": true,
  // Whether to lint Python files using pylint.
  "python.linting.pylintEnabled": false,
  // Arguments passed in. Each argument is a separate item in the array.
  "python.linting.pylintArgs": ["--ignore=C0301"],
  // Whether to lint Python files using flake8
  "python.linting.flake8Enabled": true,
  // Arguments passed in. Each argument is a separate item in the array.
  "python.linting.flake8Args": ["--ignore=E501, E402"],
  // Whether to lint Python files using pep8
  "python.linting.pep8Enabled": true,
  // Arguments passed in. Each argument is a separate item in the array.
  "python.linting.pep8Args": [
    "--ignore=E501, E402"
  ],
  // Configure glob patterns for excluding files and folders.
  "files.exclude": {
    "**/*.pyc": true,
    "**/*.xml": true
  },
  // Configure file associations to languages (e.g. "*.extension": "html"). These have precedence over the default associations of the languages installed.
  "files.associations": {
    "*.pyt": "python"
  },
  "workbench.startupEditor": "newUntitledFile",
  "window.zoomLevel": 0,
  "git.ignoreMissingGitWarning": true,
  "window.titleBarStyle": "custom"
}

Workspace Settings:

{
    "python.pythonPath": "C:\\Python27\\ArcGIS10.6\\python.exe"
}

[kraigb]

To add to this thread, "stopOnEntry" : true seems to also be a culprit, as discussed on microsoft/vscode-docs#2386. . Removing that line lets the debugger work normally.

[tchapin]

I can confirm, commenting out "stopOnEntry": true in the launch.json successfully resolves the debugger problem in 2019.1.0

A workaround would be putting a breakpoint at the first executable line to simulate the effect of stopOnEntry

[ericsnowcurrently]

There's an upstream (ptvsd) bug that is causing the debugger to stop improperly when stopOnEntry is set to true. Once that is fixed upstream and pulled into the extension we'll let you know.

[IDcard51373]

I can confirm, commenting out "stopOnEntry": true in the launch.json successfully resolves the debugger problem in 2019.1.0
A workaround would be putting a breakpoint at the first executable line to simulate the effect of stopOnEntry

That's how I deal with this problem now,,,,

I am a rookie Pythoner and juet started learning VSCode several days ago.
I study just according to https://code.visualstudio.com/docs/python/python-tutorial#_configure-and-run-the-debugger.
It took me lots of time to figure out why the DOC can work successfully while I couldn't even start......
I would have thought it was my Incorrect operation caused this problem....

[berkobob]

An alternative work around that works for me is to not install the virtual environment in the main project folder but to use a sub directory instead.

[DonJayamanne]

Closing as the upstream issue has been resolved.