Repository navigation
Active venv is activated in terminal but terminal indicates that (base) is activated #21887
Copy link
Copy link
Closed
Labels
area-terminalbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugverifiedVerification succeededVerification succeeded
Milestone
Description
Testing #21298
venv is selected as interpreter, python is activated, I see the notification, but the terminal did not activate the environment.
python logs
2023-08-29 07:52:07.238 [info] Experiment 'pythonTerminalEnvVarActivation' is active
2023-08-29 07:52:07.238 [info] Experiment 'pythonPromptNewFormatterExt' is active
2023-08-29 07:52:07.238 [info] Experiment 'pythonPromptNewToolsExt' is active
2023-08-29 07:52:07.238 [info] Experiment 'pythonTestAdapter' is active
2023-08-29 07:52:07.238 [info] Test server listening.
2023-08-29 07:52:07.238 [info] Python interpreter path: .\.venv\Scripts\python.exe
2023-08-29 07:52:11.758 [info] > & ./.venv/Scripts/Activate.ps1 ; echo 'e8b39361-0157-4923-80e1-22d70d46dee6' ; python ~/.vscode-insiders/extensions/ms-python.python-2023.15.12361009/pythonFiles/printEnvVariables.py
2023-08-29 07:52:11.758 [info] shell: powershellCore
2023-08-29 07:52:11.802 [info] > conda info --json
2023-08-29 07:52:12.006 [info] > ./.venv/Scripts/activate.bat && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode-insiders/extensions/ms-python.python-2023.15.12361009/pythonFiles/printEnvVariables.py
2023-08-29 07:52:12.006 [info] shell: commandPrompt
2023-08-29 07:52:12.707 [info] > ./.venv/Scripts/activate.bat && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode-insiders/extensions/ms-python.python-2023.15.12361009/pythonFiles/printEnvVariables.py
2023-08-29 07:52:12.707 [info] shell: commandPrompt
2023-08-29 07:52:13.699 [info] > ~\AppData\Local\Programs\Python\Python39\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\interpreterInfo.py
2023-08-29 07:52:13.810 [info] > ~\AppData\Local\Programs\Python\Python37\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\interpreterInfo.py
2023-08-29 07:52:17.817 [info] Starting Pylance language server.
2023-08-29 07:52:18.394 [info] > c:\src\vscode-jupyter\src\test\datascience\.venvnokernel\Scripts\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\interpreterInfo.py
2023-08-29 07:52:22.521 [warning] Retry failed, storage update failed for key PYTHON_ENV_INFO_CACHE
2023-08-29 07:52:24.684 [info] > c:\src\vscode-jupyter\src\test\datascience\.venvkernel\Scripts\python2.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\interpreterInfo.py
2023-08-29 07:52:25.571 [error] Error: Command failed: c:\src\vscode-jupyter\src\test\datascience\.venvkernel\Scripts\python2.exe -I c:\Users\aamunger\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\get_output_via_markers.py c:\Users\aamunger\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\interpreterInfo.py
'c:\src\vscode-jupyter\src\test\datascience\.venvkernel\Scripts\python2.exe' is not recognized as an internal or external command,
operable program or batch file.
at ChildProcess.exithandler (node:child_process:431:12)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1091:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
code: 1,
killed: false,
signal: null,
cmd: 'c:\\src\\vscode-jupyter\\src\\test\\datascience\\.venvkernel\\Scripts\\python2.exe -I c:\\Users\\aamunger\\.vscode-insiders\\extensions\\ms-python.python-2023.15.12361009\\pythonFiles\\get_output_via_markers.py c:\\Users\\aamunger\\.vscode-insiders\\extensions\\ms-python.python-2023.15.12361009\\pythonFiles\\interpreterInfo.py'
}
2023-08-29 07:52:27.591 [info] > c:\src\vscode-jupyter\src\test\datascience\.venvkernel\Scripts\python2.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\interpreterInfo.py
2023-08-29 07:52:27.721 [info] > ~\AppData\Local\Programs\Python\Python37\python.exe ~/.vscode-insiders/extensions/ms-python.python-2023.15.12361009/pythonFiles/printEnvVariables.py
2023-08-29 07:52:27.721 [info] shell: powershellCore
2023-08-29 07:52:28.808 [error] Error: Command failed: c:\src\vscode-jupyter\src\test\datascience\.venvkernel\Scripts\python2.exe -I c:\Users\aamunger\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\get_output_via_markers.py c:\Users\aamunger\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\interpreterInfo.py
'c:\src\vscode-jupyter\src\test\datascience\.venvkernel\Scripts\python2.exe' is not recognized as an internal or external command,
operable program or batch file.
at ChildProcess.exithandler (node:child_process:431:12)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1091:16)
at Socket.<anonymous> (node:internal/child_process:449:11)
at Socket.emit (node:events:513:28)
at Pipe.<anonymous> (node:net:322:12) {
code: 1,
killed: false,
signal: null,
cmd: 'c:\\src\\vscode-jupyter\\src\\test\\datascience\\.venvkernel\\Scripts\\python2.exe -I c:\\Users\\aamunger\\.vscode-insiders\\extensions\\ms-python.python-2023.15.12361009\\pythonFiles\\get_output_via_markers.py c:\\Users\\aamunger\\.vscode-insiders\\extensions\\ms-python.python-2023.15.12361009\\pythonFiles\\interpreterInfo.py'
}
2023-08-29 07:52:52.605 [info] > ~\.anaconda\Scripts\conda.exe info --json
2023-08-29 07:52:52.609 [info] > ~\.conda\Scripts\conda.exe info --json
2023-08-29 07:52:52.614 [info] > ~\.condarc\Scripts\conda.exe info --json
2023-08-29 07:52:52.651 [info] > c:\src\test\2\.conda\Scripts\conda.exe info --json
2023-08-29 07:52:52.656 [info] > c:\src\test\7\.conda\Scripts\conda.exe info --json
2023-08-29 07:52:52.660 [info] > c:\SRC\TEST\7\.CONDA\Scripts\conda.exe info --json
2023-08-29 07:52:52.665 [info] > .\.conda\Scripts\conda.exe info --json
2023-08-29 07:52:52.670 [info] > ~\AppData\Local\anaconda3\Scripts\conda.exe info --json
2023-08-29 07:52:52.830 [info] > .\.venv\Scripts\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\interpreterInfo.py
2023-08-29 07:52:52.835 [warning] c:\src\test\3\.conda\python.exe identified as Conda environment even though Conda is not found
2023-08-29 07:52:52.869 [info] > .\.conda\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\interpreterInfo.py
2023-08-29 07:57:50.337 [info] > ~\AppData\Local\Programs\Python\Python310\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\interpreterInfo.py
2023-08-29 07:57:50.589 [error] Error: Command failed: C:\Users\aamunger\AppData\Local\Programs\Python\Python310\python.exe -I c:\Users\aamunger\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\get_output_via_markers.py c:\Users\aamunger\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\interpreterInfo.py
'C:\Users\aamunger\AppData\Local\Programs\Python\Python310\python.exe' is not recognized as an internal or external command,
operable program or batch file.
at ChildProcess.exithandler (node:child_process:431:12)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1091:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
code: 1,
killed: false,
signal: null,
cmd: 'C:\\Users\\aamunger\\AppData\\Local\\Programs\\Python\\Python310\\python.exe -I c:\\Users\\aamunger\\.vscode-insiders\\extensions\\ms-python.python-2023.15.12361009\\pythonFiles\\get_output_via_markers.py c:\\Users\\aamunger\\.vscode-insiders\\extensions\\ms-python.python-2023.15.12361009\\pythonFiles\\interpreterInfo.py'
}
2023-08-29 07:57:50.597 [warning] c:\src\test\3\.conda\python.exe identified as Conda environment even though Conda is not found
2023-08-29 07:57:50.635 [info] > C:\Python310\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\interpreterInfo.py
2023-08-29 07:57:50.675 [info] > ~\AppData\Local\Programs\Python\Python311\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\interpreterInfo.py
2023-08-29 07:57:51.082 [info] > ~\AppData\Local\Microsoft\WindowsApps\python3.9.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\interpreterInfo.py
2023-08-29 07:57:52.619 [info] > ~\AppData\Local\Programs\Python\Python310\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\interpreterInfo.py
2023-08-29 07:57:52.703 [error] Error: Command failed: C:\Users\aamunger\AppData\Local\Programs\Python\Python310\python.exe -I c:\Users\aamunger\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\get_output_via_markers.py c:\Users\aamunger\.vscode-insiders\extensions\ms-python.python-2023.15.12361009\pythonFiles\interpreterInfo.py
'C:\Users\aamunger\AppData\Local\Programs\Python\Python310\python.exe' is not recognized as an internal or external command,
operable program or batch file.
at ChildProcess.exithandler (node:child_process:431:12)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1091:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
code: 1,
killed: false,
signal: null,
cmd: 'C:\\Users\\aamunger\\AppData\\Local\\Programs\\Python\\Python310\\python.exe -I c:\\Users\\aamunger\\.vscode-insiders\\extensions\\ms-python.python-2023.15.12361009\\pythonFiles\\get_output_via_markers.py c:\\Users\\aamunger\\.vscode-insiders\\extensions\\ms-python.python-2023.15.12361009\\pythonFiles\\interpreterInfo.py'
}
2023-08-29 08:02:32.678 [info] Experiment 'pythonTerminalEnvVarActivation' is active
2023-08-29 08:02:32.678 [info] Experiment 'pythonPromptNewFormatterExt' is active
2023-08-29 08:02:32.678 [info] Experiment 'pythonPromptNewToolsExt' is active
2023-08-29 08:02:32.678 [info] Experiment 'pythonTestAdapter' is active
2023-08-29 08:02:32.907 [info] Test server listening.
2023-08-29 08:02:33.002 [info] Python interpreter path: .\.venv\Scripts\python.exe
2023-08-29 08:02:34.076 [info] > & ./.venv/Scripts/Activate.ps1 ; echo 'e8b39361-0157-4923-80e1-22d70d46dee6' ; python ~/.vscode-insiders/extensions/ms-python.python-2023.15.12411005/pythonFiles/printEnvVariables.py
2023-08-29 08:02:34.076 [info] shell: powershellCore
2023-08-29 08:02:35.408 [info] > conda info --json
2023-08-29 08:02:35.699 [info] > ./.venv/Scripts/activate.bat && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode-insiders/extensions/ms-python.python-2023.15.12411005/pythonFiles/printEnvVariables.py
2023-08-29 08:02:35.699 [info] shell: commandPrompt
2023-08-29 08:02:35.842 [info] > ~\AppData\Local\Programs\Python\Python37\python.exe ~/.vscode-insiders/extensions/ms-python.python-2023.15.12411005/pythonFiles/printEnvVariables.py
2023-08-29 08:02:35.842 [info] shell: powershellCore
2023-08-29 08:02:38.472 [info] Starting Pylance language server.
2023-08-29 08:02:43.324 [info] > ~\.anaconda\Scripts\conda.exe info --json
2023-08-29 08:02:43.328 [info] > ~\.conda\Scripts\conda.exe info --json
2023-08-29 08:02:43.333 [info] > ~\.condarc\Scripts\conda.exe info --json
2023-08-29 08:02:43.343 [info] > c:\src\test\2\.conda\Scripts\conda.exe info --json
2023-08-29 08:02:43.347 [info] > c:\src\test\7\.conda\Scripts\conda.exe info --json
2023-08-29 08:02:43.351 [info] > c:\SRC\TEST\7\.CONDA\Scripts\conda.exe info --json
2023-08-29 08:02:43.355 [info] > .\.conda\Scripts\conda.exe info --json
2023-08-29 08:02:43.359 [info] > ~\AppData\Local\anaconda3\Scripts\conda.exe info --json
2023-08-29 08:03:41.548 [info] Experiment 'pythonTerminalEnvVarActivation' is active
2023-08-29 08:03:41.548 [info] Experiment 'pythonPromptNewFormatterExt' is active
2023-08-29 08:03:41.548 [info] Experiment 'pythonPromptNewToolsExt' is active
2023-08-29 08:03:41.548 [info] Experiment 'pythonTestAdapter' is active
2023-08-29 08:03:41.550 [info] Test server listening.
2023-08-29 08:03:41.574 [info] Python interpreter path: .\.venv\Scripts\python.exe
2023-08-29 08:03:43.353 [info] > conda info --json
2023-08-29 08:03:43.439 [info] > & ./.venv/Scripts/Activate.ps1 ; echo 'e8b39361-0157-4923-80e1-22d70d46dee6' ; python ~/.vscode-insiders/extensions/ms-python.python-2023.15.12411005/pythonFiles/printEnvVariables.py
2023-08-29 08:03:43.439 [info] shell: powershellCore
2023-08-29 08:03:43.520 [info] > ./.venv/Scripts/activate.bat && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode-insiders/extensions/ms-python.python-2023.15.12411005/pythonFiles/printEnvVariables.py
2023-08-29 08:03:43.521 [info] shell: commandPrompt
2023-08-29 08:03:43.804 [info] > c:\src\vscode-jupyter\src\test\datascience\.venvkernel\Scripts\python2.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\interpreterInfo.py
2023-08-29 08:03:44.353 [error] Error: Command failed: c:\src\vscode-jupyter\src\test\datascience\.venvkernel\Scripts\python2.exe -I c:\Users\aamunger\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\get_output_via_markers.py c:\Users\aamunger\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\interpreterInfo.py
'c:\src\vscode-jupyter\src\test\datascience\.venvkernel\Scripts\python2.exe' is not recognized as an internal or external command,
operable program or batch file.
at ChildProcess.exithandler (node:child_process:431:12)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1091:16)
at Socket.<anonymous> (node:internal/child_process:449:11)
at Socket.emit (node:events:513:28)
at Pipe.<anonymous> (node:net:322:12) {
code: 1,
killed: false,
signal: null,
cmd: 'c:\\src\\vscode-jupyter\\src\\test\\datascience\\.venvkernel\\Scripts\\python2.exe -I c:\\Users\\aamunger\\.vscode-insiders\\extensions\\ms-python.python-2023.15.12411005\\pythonFiles\\get_output_via_markers.py c:\\Users\\aamunger\\.vscode-insiders\\extensions\\ms-python.python-2023.15.12411005\\pythonFiles\\interpreterInfo.py'
}
2023-08-29 08:03:46.451 [info] > c:\src\vscode-jupyter\src\test\datascience\.venvkernel\Scripts\python2.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\interpreterInfo.py
2023-08-29 08:03:46.543 [error] Error: Command failed: c:\src\vscode-jupyter\src\test\datascience\.venvkernel\Scripts\python2.exe -I c:\Users\aamunger\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\get_output_via_markers.py c:\Users\aamunger\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\interpreterInfo.py
'c:\src\vscode-jupyter\src\test\datascience\.venvkernel\Scripts\python2.exe' is not recognized as an internal or external command,
operable program or batch file.
at ChildProcess.exithandler (node:child_process:431:12)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1091:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
code: 1,
killed: false,
signal: null,
cmd: 'c:\\src\\vscode-jupyter\\src\\test\\datascience\\.venvkernel\\Scripts\\python2.exe -I c:\\Users\\aamunger\\.vscode-insiders\\extensions\\ms-python.python-2023.15.12411005\\pythonFiles\\get_output_via_markers.py c:\\Users\\aamunger\\.vscode-insiders\\extensions\\ms-python.python-2023.15.12411005\\pythonFiles\\interpreterInfo.py'
}
2023-08-29 08:03:46.611 [info] Starting Pylance language server.
2023-08-29 08:03:46.870 [info] > ~\AppData\Local\Programs\Python\Python37\python.exe ~/.vscode-insiders/extensions/ms-python.python-2023.15.12411005/pythonFiles/printEnvVariables.py
2023-08-29 08:03:46.870 [info] shell: powershellCore
2023-08-29 08:03:49.997 [info] > ~\.anaconda\Scripts\conda.exe info --json
2023-08-29 08:03:50.001 [info] > ~\.conda\Scripts\conda.exe info --json
2023-08-29 08:03:50.005 [info] > ~\.condarc\Scripts\conda.exe info --json
2023-08-29 08:03:50.012 [info] > c:\src\test\2\.conda\Scripts\conda.exe info --json
2023-08-29 08:03:50.015 [info] > c:\src\test\7\.conda\Scripts\conda.exe info --json
2023-08-29 08:03:50.025 [info] > c:\SRC\TEST\7\.CONDA\Scripts\conda.exe info --json
2023-08-29 08:03:50.028 [info] > .\.conda\Scripts\conda.exe info --json
2023-08-29 08:03:50.031 [info] > ~\AppData\Local\anaconda3\Scripts\conda.exe info --json
2023-08-29 08:08:21.500 [info] Discover tests for workspace name: undefined - uri: c:\Users\aamunger\AppData\Roaming\Code - Insiders\User\settings.json
2023-08-29 08:08:27.145 [info] Discover tests for workspace name: undefined - uri: c:\Users\aamunger\AppData\Roaming\Code - Insiders\User\settings.json
2023-08-29 08:08:35.682 [info] Discover tests for workspace name: undefined - uri: c:\Users\aamunger\AppData\Roaming\Code - Insiders\User\settings.json
2023-08-29 08:08:50.865 [info] Discover tests for workspace name: undefined - uri: c:\Users\aamunger\AppData\Roaming\Code - Insiders\User\settings.json
2023-08-29 08:09:54.180 [info] > ~\AppData\Local\Programs\Python\Python310\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\interpreterInfo.py
2023-08-29 08:09:54.238 [info] > .\.venv\Scripts\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\interpreterInfo.py
2023-08-29 08:09:54.243 [warning] c:\src\test\3\.conda\python.exe identified as Conda environment even though Conda is not found
2023-08-29 08:09:54.250 [error] Error: Command failed: C:\Users\aamunger\AppData\Local\Programs\Python\Python310\python.exe -I c:\Users\aamunger\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\get_output_via_markers.py c:\Users\aamunger\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\interpreterInfo.py
'C:\Users\aamunger\AppData\Local\Programs\Python\Python310\python.exe' is not recognized as an internal or external command,
operable program or batch file.
at ChildProcess.exithandler (node:child_process:431:12)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1091:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
code: 1,
killed: false,
signal: null,
cmd: 'C:\\Users\\aamunger\\AppData\\Local\\Programs\\Python\\Python310\\python.exe -I c:\\Users\\aamunger\\.vscode-insiders\\extensions\\ms-python.python-2023.15.12411005\\pythonFiles\\get_output_via_markers.py c:\\Users\\aamunger\\.vscode-insiders\\extensions\\ms-python.python-2023.15.12411005\\pythonFiles\\interpreterInfo.py'
}
2023-08-29 08:09:54.278 [info] > .\.conda\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\interpreterInfo.py
2023-08-29 08:09:54.539 [info] > C:\Python310\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\interpreterInfo.py
2023-08-29 08:09:54.561 [info] > ~\AppData\Local\Programs\Python\Python311\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\interpreterInfo.py
2023-08-29 08:09:54.729 [info] > ~\AppData\Local\Programs\Python\Python37\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\interpreterInfo.py
2023-08-29 08:09:54.744 [info] > ~\AppData\Local\Programs\Python\Python39\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\interpreterInfo.py
2023-08-29 08:09:54.942 [info] > ~\AppData\Local\Microsoft\WindowsApps\python3.9.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\interpreterInfo.py
2023-08-29 08:09:56.272 [info] > ~\AppData\Local\Programs\Python\Python310\python.exe -I ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\get_output_via_markers.py ~\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\interpreterInfo.py
2023-08-29 08:09:56.330 [error] Error: Command failed: C:\Users\aamunger\AppData\Local\Programs\Python\Python310\python.exe -I c:\Users\aamunger\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\get_output_via_markers.py c:\Users\aamunger\.vscode-insiders\extensions\ms-python.python-2023.15.12411005\pythonFiles\interpreterInfo.py
'C:\Users\aamunger\AppData\Local\Programs\Python\Python310\python.exe' is not recognized as an internal or external command,
operable program or batch file.
at ChildProcess.exithandler (node:child_process:431:12)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1091:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
code: 1,
killed: false,
signal: null,
cmd: 'C:\\Users\\aamunger\\AppData\\Local\\Programs\\Python\\Python310\\python.exe -I c:\\Users\\aamunger\\.vscode-insiders\\extensions\\ms-python.python-2023.15.12411005\\pythonFiles\\get_output_via_markers.py c:\\Users\\aamunger\\.vscode-insiders\\extensions\\ms-python.python-2023.15.12411005\\pythonFiles\\interpreterInfo.py'
}
2023-08-29 08:14:16.888 [warning] c:\src\test\3\.conda\python.exe identified as Conda environment even though Conda is not found
2023-08-29 08:17:13.796 [warning] c:\src\test\3\.conda\python.exe identified as Conda environment even though Conda is not found
2023-08-29 08:17:21.099 [warning] c:\src\test\3\.conda\python.exe identified as Conda environment even though Conda is not found
2023-08-29 08:17:21.332 [warning] c:\src\test\3\.conda\python.exe identified as Conda environment even though Conda is not found
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area-terminalbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugverifiedVerification succeededVerification succeeded

Activity
amunger commentedon Aug 29, 2023
repros for pwsh, cmd, wsl, git bash - I get the pop up notification, but no environment activated
karrtikr commentedon Aug 29, 2023
Aaron Munger (@amunger) Did you run
to verify which environment is actually activated as per the TPI?
karrtikr commentedon Aug 29, 2023
We only show the pop up notification when we cannot indicate using a terminal prompt that an env is activated.
amunger commentedon Aug 29, 2023
oh, I really expected to see the environment name in the terminal prompt, but it looks like it is activated from running that command.
This can probably be closed but I am really not looking forward to yet another pop-up from the python extension every time I create a new profile.
karrtikr commentedon Aug 29, 2023
It's only a one time notification ("Don't show again" button), so you shouldn't see it every time you create a profile. But I understand it's still not ideal.
A notification is unfortunately the only way to avoid confusion such as this issue, we had a team discussion in UX and API sync and we arrived to this conclusion: microsoft/vscode#188969 (comment).
karrtikr commentedon Aug 29, 2023
I'll amend the notification to clarify this detail 👍
[-]active venv not auto activated in terminal[/-][+]Active venv is activated in terminal but terminal indicates that `(base)` is activated[/+]Call out that env name may not show in terminal activation notificati…
karrtikr commentedon Aug 30, 2023
Aaron Munger (@amunger) Thanks for bringing this up today. FYI as Karthik pointed out, I've improved this further for non-Windows in #21902 and opened a new issue to see if we can do anything for Windows: #21903.
Call out that env name may not show in terminal activation notificati…
Merged PR posit-dev/positron-python#213: Merge python extension relea…
Merged PR posit-dev/positron-python#213: Merge python extension relea…