Repository navigation
Pipenv environments list on the side bar does not shows the venv name as label. #824
Copy link
Copy link
Closed
Labels
author-verification-requestedIssues potentially verifiable by issue authorIssues potentially verifiable by issue authorbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugtriage-neededverifiedVerification succeededVerification succeeded
Milestone
Description
Activity
ah yes that is confusing- let me put in a fix. Thanks for reporting!
Reacted by Carlos Bazaga- addedbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug
on Sep 11, 2025 - added a commit that references this issue
on Sep 22, 2025 👏 👏 👏
Did it work Carlos Bazaga (@Carbaz)? If so I can mark it as such for the team- thanks!
- addedauthor-verification-requestedIssues potentially verifiable by issue authorIssues potentially verifiable by issue author
on Sep 23, 2025 - addedinfo-neededIssue requires more information from posterIssue requires more information from poster
on Sep 23, 2025 Not yet checked, I'll give it a shot tomorrow and feedback here.
Reacted by Eleanor Boyd- removedinfo-neededIssue requires more information from posterIssue requires more information from poster
on Sep 23, 2025 Eleanor Boyd (@eleanorjboyd) I switched to the pre-release version and it seems to work perfectly, thanks! 👏 👏 👏

- added a commit that references this issue
on Oct 23, 2025 - locked as resolved and limited conversation to collaborators
on Apr 30, 2026
Metadata
Metadata
Assignees
Labels
author-verification-requestedIssues potentially verifiable by issue authorIssues potentially verifiable by issue authorbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugtriage-neededverifiedVerification succeededVerification succeeded
The side bar list view for Pipenv environments detected does not uses the folder name, which can only be seen by hoovering.
This makes this list really hard to work with if the number of environments is high, more than 3 would be high to me, which is common not only because Pipenv uses a centralized folder for them all, it's also usual to have projects with several services each one has its own folder with its own environment.
The virtual env name, the folder name, should be used as the label of the list directly, as it does for Venv environments and as it does the old extension: