Skip to content

Conversation

@eleanorjboyd
Copy link
Member

This PR enhances the "Select Interpreter" dropdown in the Python Environments extension by including the full path to each interpreter in the description text, making it easier for users to identify and distinguish between different Python environments.

(copilot did this via eleanorjboyd#1 but the PR was created wrong)

fixes #593

@eleanorjboyd eleanorjboyd self-assigned this Jul 9, 2025
@eleanorjboyd eleanorjboyd added the bug Issue identified by VS Code Team member as probable bug label Jul 9, 2025
@vs-code-engineering
Copy link

⚠️ This PR originates from a fork. Due to security restrictions, pipelines from forks are no longer triggered automatically. Learn more.

If the changes appear safe, you can manually trigger the pipeline by commenting /AzurePipelines run.

@vs-code-engineering vs-code-engineering bot added this to the July 2025 milestone Jul 9, 2025
@eleanorjboyd eleanorjboyd merged commit 02d713a into microsoft:main Jul 9, 2025
6 checks passed
NguyenCuong1989 referenced this pull request in NguyenCuong1989/vscode-python-environments Oct 23, 2025
This PR enhances the "Select Interpreter" dropdown in the Python
Environments extension by including the full path to each interpreter in
the description text, making it easier for users to identify and
distinguish between different Python environments.

(copilot did this via
eleanorjboyd/vscode-python-environments#1 but
the PR was created wrong)

fixes microsoft/vscode-python-environments#593

---------

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Issue identified by VS Code Team member as probable bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Names in "Select a Python Environment" drop down are too brief

2 participants