Skip to content

Interpreter discovery experiment: Relative interpreter path shown doesn't have ~ #15312

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
kimadeline opened this issue Feb 3, 2021 · 1 comment · Fixed by #15495
Closed

Interpreter discovery experiment: Relative interpreter path shown doesn't have ~ #15312

kimadeline opened this issue Feb 3, 2021 · 1 comment · Fixed by #15495
Assignees
@karrtikr
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority regression Bug didn't exist in a previous release

Comments

@kimadeline
Copy link

Environment data

  • VS Code version: 1.53.0-insider, commit 8490d3dde47c57ba65ec40dd192d014fd2113496
  • Extension version (available under the Extensions sidebar): 2021.2.531887795-dev
  • OS and version: macOS Big Sur (11.2)
  • Opted into all experiments ('All')

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]

Expected behaviour

If the interpreter path shown is relative to the user home folder, prefix it with ~. Otherwise, show absolute path.

Actual behaviour

Some relative paths don't start with ~:

image
@kimadeline kimadeline added bug Issue identified by VS Code Team member as probable bug triage-needed Needs assignment to the proper sub-team labels Feb 3, 2021
@karthiknadig karthiknadig added area-environments Features relating to handling interpreter environments needs PR important Issue identified as high-priority labels Feb 4, 2021
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Feb 4, 2021
@karthiknadig
Copy link
Member

Related #15289

@kimadeline kimadeline mentioned this issue Feb 17, 2021
Closed
@brettcannon brettcannon added the regression Bug didn't exist in a previous release label Feb 22, 2021
@karrtikr karrtikr self-assigned this Feb 24, 2021
@karrtikr karrtikr mentioned this issue Feb 24, 2021
Merged
@ghost ghost removed the needs PR label Feb 24, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@karrtikr karrtikr

Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority regression Bug didn't exist in a previous release
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Ensure Posix Path locator doesn't return relative binary paths karrtikr/vscode-python
4 participants
@brettcannon @karthiknadig @karrtikr @kimadeline