Repository navigation
pipenv not returning environment following reload #1206
Description
Activity
- added a commit that references this issue
on Apr 22, 2026 - added a commit that references this issue
on Apr 30, 2026 🤖 Triage: is the Pipenv environment still missing after Reload Window with the current Python Environments and Pipenv versions? If so, please share the project’s relevant
python-envs.pythonProjectsand default-manager settings, the Python Environments trace from immediately before and after reload, and whetherpipenv --venvresolves the same path both times. We need this to identify which part of reload loses the environment.🤖 Tested:
Scenarios tested:
- Workspace-root project with a project-local Pipenv
.venv. - Workspace-root project with an external Pipenv environment stored under
WORKON_HOME. - Nested Python project with an explicit Pipenv entry in
python-envs.pythonProjectsand an external Pipenv environment.
All three passed. After reload, without reselecting the environment:
- The public API returned the same selected environment.
- The backing environment lookup used by the Projects view returned that environment, including the initial lookup before explicitly enumerating environments.
- The effective project/default-manager settings were preserved.
pipenv --venvreturned the same path.- Running the selected interpreter directly produced the expected
sys.prefix.
Test setup: macOS ARM64; local Python Environments 1.39.0 build at commit
f0648b9d; VS Code 1.139.1; Python extension 2026.6.0 loaded; Pipenv 2025.0.4. Each scenario used an isolated VS Code profile.I could not reproduce the reported failure on this checkout.
- Workspace-root project with a project-local Pipenv
I have one project set with pipenv as the environment manager. I have selected a pipenv environment and it is going great- the environment is selected in the project UI and being used in all execution scenarios. But then when I reload the entire window, the project manager view reports that "pipenv didn't not return an environment" or something like this. The setting is correct (still points to pipenv) but somehow the env we set prior to reload is not being loaded again.