forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed
Labels
area-debuggingbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buggood first issue
Milestone
Description
Environment data
VS Code version: 1.19.1
Python Extension version: 0.9.1
Python Version: 3.6.3
OS and version: Windows 10 (10.0.16299 Build 16299)
Actual behavior
On Windows when a python launch configuration is used where Pyramid
is included in the configuration's debugOptions
list, the extension tries to launch the wrong program. Instead of launching pserve.exe
, the extension tries to launch pserve
which results in an error.
File does not exist. "[Workspace Directory]\partfinder\env\Scripts\pserve"
Expected behavior
The appropriate program (pserve.exe
) should be launched.
Steps to reproduce:
- On Windows, install Visual Studio Code with the
ms-python.python
extension. - Create a new folder and open it with Visual Studio Code.
- Set up a virtual environment with
python -m venv env
. - Install Pyramid with
env/Scripts/pip.exe install pyramid
. - Configure your
python.pythonPath
setting for your workspace, by saving the following into.vscode/settings.json
:
{
"python.pythonPath": "${workspaceFolder}/env/Scripts/python.exe"
}
- Save the following into
.vscode/launch.json
:
{
"version": "0.2.0",
"configurations": [
{
"name": "Python: Pyramid",
"type": "python",
"request": "launch",
"stopOnEntry": true,
"pythonPath": "${config:python.pythonPath}",
"cwd": "${workspaceFolder}",
"env": {},
"envFile": "${workspaceFolder}/.env",
"args": [
"${workspaceFolder}/development.ini"
],
"debugOptions": [
"RedirectOutput",
"Pyramid"
]
}
]
}
- Try to start debugging, using the
Python: Pyramid
launch configuration
Logs
Output from Python
output panel
[Nothing is outputted]
Output from Console window
(Help->Developer Tools menu)
messageService.ts:126 File does not exist. "[Workspace Folder]\partfinder\env\Scripts\pserve"
Metadata
Metadata
Assignees
Labels
area-debuggingbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buggood first issue