-
Notifications
You must be signed in to change notification settings - Fork 31
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginfo-neededIssue requires more information from posterIssue requires more information from poster
Description
Unable to handle /path/to/python.exe error occurs when the vscode configuration folder (like .vscode) is a symbolic link, which usually occurs when vscode installed in scoop or other vscode configuration folders are symlinked Here I have changed the vscode installed on the system to use symbolic links
2025-04-07 18:51:08.594 [info] Starting Python Locator c:\Users\bash\.vscode\extensions\ms-python.vscode-python-envs-0.3.10731009-win32-x64\python-env-tools\bin\pet.exe server
2025-04-07 18:51:08.594 [info] Using conda from settings: conda
2025-04-07 18:51:08.594 [info] Conda not found, turning off conda features. [TypeError: Cannot read properties of undefined (reading 'filePath')
at c:\Users\bash\.vscode1\extensions\ms-python.vscode-python-envs-0.3.10731009-win32-x64\dist\extension.js:2:273856
at Array.find (<anonymous>)
at t.getCallingExtension (c:\Users\bash\.vscode1\extensions\ms-python.vscode-python-envs-0.3.10731009-win32-x64\dist\extension.js:2:273842)
at h (c:\Users\bash\.vscode1\extensions\ms-python.vscode-python-envs-0.3.10731009-win32-x64\dist\extension.js:2:304750)
at t.PythonEnvironmentManagers.registerEnvironmentManager (c:\Users\bash\.vscode1\extensions\ms-python.vscode-python-envs-0.3.10731009-win32-x64\dist\extension.js:2:305670)
at f.registerEnvironmentManager (c:\Users\bash\.vscode1\extensions\ms-python.vscode-python-envs-0.3.10731009-win32-x64\dist\extension.js:2:322280)
at t.registerCondaFeatures (c:\Users\bash\.vscode1\extensions\ms-python.vscode-python-envs-0.3.10731009-win32-x64\dist\extension.js:2:446391)
at async Promise.all (index 1)]
2025-04-07 18:51:08.785 [error] Unable to handle f:\Scoop\apps\python\3.13.2\python.exe
2025-04-07 18:51:09.523 [error] No environment managers registered
2025-04-07 18:51:09.536 [error] Unable to handle f:\Scoop\apps\python\3.13.2\python.exe
2025-04-07 18:51:09.607 [error] Unable to handle f:\Scoop\apps\python\3.13.2\python.exe
2025-04-07 18:51:09.610 [error] Unable to handle f:\Scoop\apps\python\3.13.2\python.exe
2025-04-07 18:51:09.613 [error] Unable to handle f:\Scoop\apps\python\3.13.2\python.exe
2025-04-07 18:51:09.671 [error] Unable to handle f:\Scoop\apps\python\3.13.2\python.exe
2025-04-07 18:51:18.995 [error] No environment managers registered
2025-04-07 18:51:19.031 [error] Unable to handle f:\Scoop\apps\python\3.13.2\python.exe
2025-04-07 18:51:19.032 [error] Unable to handle f:\Scoop\apps\python\3.13.2\python.exe
2025-04-07 18:51:19.034 [error] Unable to handle f:\Scoop\apps\python\3.13.2\python.exe
2025-04-07 18:51:19.035 [error] Unable to handle f:\Scoop\apps\python\3.13.2\python.exe
And the issues I sent before were installed using scoop #132
It works fine when the configuration folder does not use symbolic links
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginfo-neededIssue requires more information from posterIssue requires more information from poster