Repository navigation
Debugger does not work in a venv installation of Python #1288
Description
Environment data
- VS Code version: 1.21.1
- Extension version (available under the Extensions sidebar): 2018.3.1
- OS and version: MacOS 10.13.4
- Python version (& distribution if applicable, e.g. Anaconda): 3.6.4
- Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
- Relevant/affected Python packages and their versions: None
Actual behavior
All breakpoints are ignored when debugging Python from inside a venv.
Expected behavior
Breakpoints are not ignored.
Steps to reproduce:
Using:
import sys
print(sys.version)
print(sys.executable)
Put a breakpoint on line 2
Logs
Output for Python in the Output pane
Output from Console under the Developer Tools panel
3.6.4 (v3.6.4:d48ecebad5, Dec 18 2017, 21:07:28)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)]
/Users/chris/Code/Python/np/bin/python
Configuration Files
launch.json
{
"name": "Python: Current File",
"type": "python",
"request": "launch",
"pythonPath": "/Users/chris/Code/np/bin/python",
"program": "${file}"
}
settings.json
{
"python.pythonPath":"/Users/chris/Code/np/bin/python",
"python.autoComplete.addBrackets": true
}
Notes
When I run the same code using the system installation the debugger works fine.
The issue also only persists when the type is set to python and not when it is set to pythonExperimental.
Activity
brettcannon commentedon Apr 9, 2018
Obviously this is weird since others can debug on macOS. Are you using the macOS build of CPython from python.org? (I'm just guessing at what might be different about your setup.)
ReagentX commentedon Apr 12, 2018
I have Python 3.6.5 installed from Python.org and I created the
venvusingpython3 -m venv /path/to/new/virtual/environment, which to my knowledge is not out of the ordinary.ReagentX commentedon Apr 18, 2018
It seems to only affect this one
venvand not any others I create work fine. Since I have no way of reproducing this issue I think it is reasonable to close this issue.brettcannon commentedon Apr 18, 2018
Sorry we never figured out the cause.