Skip to content

Select interpreter at workspace level doesn't have any effect #17854

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

Closed
rchiodo opened this issue Oct 26, 2021 · 3 comments
Closed

Select interpreter at workspace level doesn't have any effect #17854

rchiodo opened this issue Oct 26, 2021 · 3 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 investigating We are looking into the cause of the issue

Comments

@rchiodo
Copy link

rchiodo commented Oct 26, 2021

Environment data

  • VS Code version: Latest insiders
  • Extension version (available under the Extensions sidebar): 2021.11.1382879425-dev
  • OS and version: Windows 10
  • Python version (& distribution if applicable, e.g. Anaconda): XXX

[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

Selecting an interpreter at the workspace level would allow it to be used

Actual behaviour

Selecting an interpreter at the workspace level has no effect

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

  1. Create new workspace file
  2. Add a folder with python files in it to the workspace
  3. Run 'Select intepreter'
  4. Pick the 'workspace level' option
  5. Pick an interpreter
    Interpreter is not set in the UI:
    image
    Interpreter does not seem to be used when starting a terminal

Logs

python-output-log.txt

@rchiodo rchiodo added bug Issue identified by VS Code Team member as probable bug triage-needed Needs assignment to the proper sub-team labels Oct 26, 2021
@karthiknadig karthiknadig added area-environments Features relating to handling interpreter environments triage and removed triage-needed Needs assignment to the proper sub-team labels Oct 27, 2021
@karrtikr karrtikr added investigating We are looking into the cause of the issue and removed triage labels Oct 27, 2021
@karrtikr
Copy link

karrtikr commented Oct 27, 2021

I'm unable to reproduce this issue.

I think your workspace folder might have d:\Source\Testing\storeEnv\Scripts\python.exe selected (which is an invalid interpreter) because of which settings at workspace level has no effect. Can you try clearing the workspace folder setting first using Python: Clear workspace interpreter command.

@karrtikr karrtikr added the info-needed Issue requires more information from poster label Oct 27, 2021
@rchiodo
Copy link
Author

rchiodo commented Oct 27, 2021

Hmm, not reproing anymore. Even without the clear workspace interpreter.

@rchiodo rchiodo closed this as completed Oct 27, 2021
@karrtikr
Copy link

I also noticed that sometimes when an interpreter is changed for a workspace folder, we also need to change the currently active editor file for the changes to reflect, it may also have been that.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 27, 2021
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 investigating We are looking into the cause of the issue
Projects
None yet
Development

No branches or pull requests

3 participants