venv environments are not detected until folder is opened

[aayushkatariaa]

Environment data

• VS Code version: 1.80.1 (User Setup)
• Jupyter Extension version (available under the Extensions sidebar): v2023.6.1101941928
• Python Extension version (available under the Extensions sidebar): v2023.12.0
• OS (Windows | Mac | Linux distro) and version: Windows 10, V10.0.19045 Build 19045
• Python and/or Anaconda version: 3.11.4
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
• Jupyter server running: Local

Expected behaviour

Environments in the same folder are detected under select kernels

Actual behaviour

Only the system interpreter is detected

Steps to reproduce:

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

1. Create an ipynb file with some code in a folder and initialize a venv in the same.
2. Try to open that file without opening the folder from your explorer.

Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)

[DonJayamanne]

Than you for filling this issues, however the steps area not sufficient to replicate this issue
Please could you provide steps to repro issue

• What use the folder structure like
• Where is the ven in the folder
• Can you see the env in the python interpreter list
• What folder do you open in vscode?

[aayushkatariaa]

• This is the structure
  
• venv is inside the folder? not sure what is expected here
• No, the environment does not show up in the interpreter list either
• None, I open the file without opening any folder

[karrtikr]

Please provide the debug logs which can help diagnose the issue:

• Run Developer: Set log level command

• Select Python -> Select Trace

• Run Developer: Reload Window command

• Provide the output:

  Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

  XXX
  

[aayushkatariaa]

note that the company name has been changed due to privacy reasons along with some other minor edits
log.txt

[karrtikr]

Does venv environments show up when using Python: Select Interpreter command?

[karrtikr]

Thanks for the bug report! We investigate issues in order based on priority and severity, which includes the impact it has on your ability to use the extension to do productive work, and the number of people affected. If other users come forward and leave a comment demonstrating they are seeing/reproducing the problem then we will raise this issue's priority. Thanks for understanding and the patience!

[aayushkatariaa]

Does venv environments show up when using Python: Select Interpreter command?

As mentioned previously, no it does not

[aayushkatariaa]

Also this issue may also be related to #21633 although I'm not a 100% sure on that

[karrtikr]

Try to open that file without opening the folder from your explorer.

It seems to be that no workspace folder is opened, is that the case?

[aayushkatariaa]

Yeah

[karrtikr]

You need a workspace folder to be opened for workspace specific environments to be discovered. There is no way for us to know which project to look for environments in otherwise.

[karrtikr]

Try 'File-> Open folder...' option

[karrtikr]

Closing as this seems to be the intended behavior.

[aayushkatariaa]

Try 'File-> Open folder...' option

You need a workspace folder to be opened for workspace specific environments to be discovered. There is no way for us to know which project to look for environments in otherwise.

So is it intended that environments that are present in such folders do not show up?

[aayushkatariaa]

Since it kind of limits functionality so i thought it'd at least look in the same folder as the opened file