Closed
Description
Today I just stumbled across python debugging/running when using "integratedTerminal" is not working anymore. As far as I remind, last week it worked without an an issue. I alos upgrade to most recent version today now but the problem still exists
Environment data
- VS Code version: 1.39.2
- Extension version (available under the Extensions sidebar): 2019.10.44104
- OS and version: Linux x64 4.14.11-amd64
- Python version (& distribution if applicable, e.g. Anaconda): Devuan/Debian 2.7
- Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
- Relevant/affected Python packages and their versions: N/A
- Jedi or Language Server? (i.e. what is
"python.jediEnabled"
set to; more info How to update the language server to the latest stable version #3977): N/A
Expected behaviour
Python script is started and executes
Actual behaviour
I can see the "Python Debug Console" flash up show some printouts and immediately closes. The debug bar at top of screen vanishes after some seconds and error popup "error launching..." is displayed.
Steps to reproduce:
- Press [F5] or [CTRL]+ [F5]
Logs
N/A
Files
launch.json (not working)
{
"version": "0.2.0",
"configurations": [
{
"name": "Python: Run testcase file",
"type": "python",
"request": "launch",
"program": "${file}",
"console": "integratedTerminal",
"env" : {
"PYTHONPATH" : "${workspaceFolder}"
}
}
]
}
launch.json (working)
{
"version": "0.2.0",
"configurations": [
{
"name": "Python: Run testcase file",
"type": "python",
"request": "launch",
"program": "${file}",
"console": "internalConsole",
"env" : {
"PYTHONPATH" : "${workspaceFolder}"
}
}
]
}
settings.json
{
"workbench.colorTheme": "Solarized Light",
"telemetry.enableCrashReporter": false,
"telemetry.enableTelemetry": false,
"editor.renderWhitespace": "all",
"files.trimTrailingWhitespace": true,
"window.zoomLevel": 1,
"terminal.integrated.shell.linux": "/usr/bin/env",
"terminal.integrated.shellArgs.linux": [
"LANG=de_DE@utf-8",
"/bin/bash"
],
}
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
karthiknadig commentedon Nov 6, 2019
@amesser Do you see any error in the terminal? Or in the output panel for Python.
amesser commentedon Nov 6, 2019
Unfortunately not. In error case, I see VS code console switches for a very short time to "Python Debug Console" but immediately closes it again. The console seems to be filled with some output which looks like environment variable assignments, but I'm not fully sure. There is neither an error output in a terminal from which I started VS code nor in the other console windows in VS code.
Can I set something in VS code which makes it to not close the console or to produce more debug output to stdout/stderr? It looks to me that VS code always forks to background when starting from a terminal?
karthiknadig commentedon Nov 6, 2019
@amesser Can you share the output of this panel? You may have to scroll all the way to the top to see this:

amesser commentedon Nov 6, 2019
Will do later. (Have no access to the machine at the moment)
amesser commentedon Nov 6, 2019
@karthiknadig Here we go
Output/Python
and Output/Log(Window), seems to be more promising:
Later log let me think it might be a more general problem and not related to vs python?
karthiknadig commentedon Nov 7, 2019
@amesser Looks like this is microsoft/node-pty#220
2 remaining items