Skip to content
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.

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

Unclear which python is used #21881

Closed
aeschli opened this issue Aug 29, 2023 · 7 comments
Closed

Unclear which python is used #21881

aeschli opened this issue Aug 29, 2023 · 7 comments
Assignees
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team

Comments

@aeschli
Copy link

aeschli commented Aug 29, 2023

Testing #21878

I'm a python novice, so feel free to close the issue if all is working as expected

  • create a new folder with a hellp.py file
  • on the command line in that folder create a virtual environment with python3 -m venv env
  • open the hello.py file in VS Code

The test issue says ensure that the selected python is the one from pre-existing .venv.

  • I hover over the python version in the status bar: it says /bin/python3
  • I click on the python version in the status bar. The quick pick says: Selected interpreter: ./env/bin/python
  • The quick pick also has a star. I'm not sure what the star means. Is it because it is selected, or because it is recommended...

Image

So which one is now selected?

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Aug 29, 2023
@karthiknadig
Copy link
Member

karthiknadig commented Aug 29, 2023

@aeschli In the Quick Pick placeholder it shows you the path to the python that is selected. Are you suggesting more of visual icon on the path to the python in the quickpick list?
Edit: I see the status is showing a different version @karrtikr This looks like a status bar update bug.
/cc @luabud @cwebster-99

@github-actions github-actions bot added the info-needed Issue requires more information from poster label Aug 29, 2023
@karthiknadig karthiknadig added bug Issue identified by VS Code Team member as probable bug needs proposal Need to make some design decisions area-environments Features relating to handling interpreter environments info-needed Issue requires more information from poster and removed info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team labels Aug 29, 2023
@karthiknadig karthiknadig removed their assignment Aug 30, 2023
@karrtikr karrtikr added triage-needed Needs assignment to the proper sub-team and removed info-needed Issue requires more information from poster labels Aug 30, 2023
@aeschli
Copy link
Author

aeschli commented Aug 30, 2023

I was confused that the hover in the status bar seems to contradict what the quick pick says.
So the bug might be in the status bar then.

@karrtikr
Copy link

karrtikr commented Sep 5, 2023

The quick pick also has a star. I'm not sure what the star means. Is it because it is selected, or because it is recommended...

We have plans to re-evaluate the icons and way to highlight recommended or selected interpreter: #19904 #20275.

Unfortunately I'm unable to reproduce the status bar bug. For me "env" shows up in the status bar as well. Working with @karthiknadig internally to see if he can repro.

@github-actions github-actions bot added the info-needed Issue requires more information from poster label Sep 5, 2023
@karrtikr karrtikr removed the needs proposal Need to make some design decisions label Sep 5, 2023
@karrtikr
Copy link

karrtikr commented Sep 5, 2023

@aeschli Apologies, we thought we had the repro but unfortunately are not able to right now. Here's what we tried:

  • Select a pre-existing .venv (env folder name is ".venv")
  • Attempt to Create env, choose re-create
  • Things seem to be normal, with status bar pointing to .venv

Would appreciate you helping with the exact steps to follow to land in this situation, where status bar is different from what picker says.

@github-actions
Copy link

github-actions bot commented Oct 6, 2023

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

Happy Coding!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 6, 2023
@karthiknadig karthiknadig reopened this Oct 6, 2023
@karrtikr
Copy link

karrtikr commented Oct 6, 2023

@karthiknadig @aeschli Let me know if any of you are able to provide the repro steps.

@karrtikr karrtikr added info-needed Issue requires more information from poster and removed info-needed Issue requires more information from poster labels Oct 6, 2023
@karrtikr
Copy link

karrtikr commented Nov 1, 2023

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.

@karrtikr karrtikr closed this as not planned Won't fix, can't repro, duplicate, stale Nov 1, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team
Projects
None yet
Development

No branches or pull requests

3 participants