Error: spawn $ {workspaceFolder}\.env\Scripts\python.exe ENOENT

[FlavioCestari]

Environment data

VS Code version: 1.20.1
Python Extension version: 2018.1
Python Version: 3.6.3
OS and version: Windows 7 Enterprise

Actual behavior

After starting debugging (using default Python configuration template), I get this error:

• Debug console: Error: spawn $ {workspaceFolder}\.env\Scripts\ python.exe ENOENT
• Alert message: Failed to launch the Python Process, please validate the path $ {workspaceFolder}\.env\Scripts\python.exe

After starting debugging, but using "Python: Terminal (integrated)" configuration template, I get the error below and the debug feature stops working (it's not possible to debug again unless restart VSCode):

C:\{project-path}>cd c:\{project-path} && cmd /C "set "PYTHONIOENCODING=UTF-8" && set "PYTHONUNBUFFERED=1" && ${workspaceFolder}.virtualenv\Scripts\python.exe C:\Users\{username}\.vscode\extensions\ms-python.python-2018.1.0\pythonFiles\PythonTools\visualstudio_py_launcher.py c:\{project-path} 60668 34806ad9-833a-4524-8cd6-18ca4aa74f14 DUMMYVALUE c:\{project-path}\startfile.py
"The system cannot find the path specified."

This issue occurs after VSCode's upgrade to 1.20.x version.

ps .: ".env" is my virtualenv directory.

Expected behavior

debugging normally

Steps to reproduce:

• Open VSCode
• Open folder ou workspace
• Click in Start Debugging button or Debug>Start Debugging menu or type [F5].

[FlavioCestari]

I tried renaming the virtualenv directory (.env) to .virtualenv but got the same error.

Steps to rename virtualenv:

1. > rm -r .env
2. > virtualenv .virtualenv
3. > .virtualenv\Scripts\activate
4. (.virtualenv) > pip install -r requirements.txt
5. > deactivate

[FlavioCestari]

launch.json file:

{
    "version": "0.2.0",
    "configurations": [

        {
            "name": "Python",
            "type": "python",
            "request": "launch",
            "stopOnEntry": true,
            "pythonPath": "${config:python.pythonPath}",
            "program": "${file}",
            "cwd": "${workspaceFolder}",
            "env": {},
            "envFile": "${workspaceFolder}/.env",
            "debugOptions": [
                "RedirectOutput"
            ]
        },
        {
            "name": "Python: Terminal (integrated)",
            "type": "python",
            "request": "launch",
            "stopOnEntry": true,
            "pythonPath": "${config:python.pythonPath}",
            "program": "${file}",
            "cwd": "${workspaceFolder}",
            "console": "integratedTerminal",
            "env": {},
            "envFile": "${workspaceFolder}/.env",
            "debugOptions": []
        }
    ]
}

settings.json file:

{
    "python.pythonPath": "${workspaceFolder}\\.virtualenv\\Scripts\\python.exe"
}

[DonJayamanne]

Duplicate of #691

The fix will be in the next release (end of this month).

Until then please use the Insiders build of this extension as it contains the fix (Note: I'm not referring to VS Code Insiders).

The instructions to download and install this insiders build of the extension can be found here, under Insiders Buid

[hash]

@DonJayamanne the odd thing is happening on linux Fedora 27 xfce, fresh virtual machine.
I have "pythonPath": "${config:python.pythonPath}", in launch.json
I get Error: spawn ${workspaceFolder}/.venv/bin/python ENOENT when trying to debug,
I change it to "pythonPath": "${workspaceFolder}/.venv/bin/python", same path is in settings.json
it works, then I change it back to "pythonPath": "${config:python.pythonPath}",
it STILL! works. I restart VSCode and it stops working.

I am using insiders build that is reporting version 2018.2.0-beta and VSCode 1.20.1 .

[DonJayamanne]

@hash
It works at this end. Its possible something isn't setup correctly at your end.

• Please uninstall all python extensions
• Download and re-install the latest version of the insiders build (once again)
• Wait for the prompt to re-start VS Code
• Test debugging

[hash]

Ok, I am now able to reproduce the error when I try to debug just after VSCode starts, but not after some seconds pass.
So not an issue.

[awhillas]

I'm still getting this error even after disabling all extensions (except this one of course). Yes "I've tried turning it off and on again" (somethings never change with M$ products :D)

Error: spawn /Users/alex/dev/venv/ingest-sU4WTsve/bin/python ENOENT

using pipenv and vscode Version 1.22.1 (1.22.1)

[DonJayamanne]

@awhillas
have you tried uninstalling and re-installing (two comments up, #853 (comment))

[awhillas]

@DonJayamanne yes, no dice :(

[DonJayamanne]

Please create another issue if you are still experiencing this issue, This has been closed.