You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected: Venv detected according to venvFolders setting.
Actual: Venv sometimes not detected when they should; sometimes detected when they should not.
Steps to reproduce:
Have this in your settings:
"python.venvFolders": [
"${workspaceFolder}/output/env",
"${workspaceFolder}/output",
"output/env", // Unsure if this means the same as above
"output"
]
Create new directory with file.py.
Create venv at output/env, confirm it is not detected by the extension (it should be).
Create venv at env, confirm it is detected by the extension (why? Explicitly not configured for that).
Create venv at env2, confirm it is detected by the extension (it should not be, what's the meaning of the setting otherwise).
Diagnostic data
Python version (& distribution if applicable, e.g. Anaconda): 3.11.3
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Global
Value of the python.languageServer setting: Jedi
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
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!
python.venvFolder setting is only meant to refer to folders directly under home directory, so none of the configs work. You probably want to use python.venvPath setting:
Type: Bug
Behaviour
Expected vs. Actual
Expected: Venv detected according to
venvFolders
setting.Actual: Venv sometimes not detected when they should; sometimes detected when they should not.
Steps to reproduce:
output/env
, confirm it is not detected by the extension (it should be).env
, confirm it is detected by the extension (why? Explicitly not configured for that).env2
, confirm it is detected by the extension (it should not be, what's the meaning of the setting otherwise).Diagnostic data
python.languageServer
setting: JediOutput for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)User Settings
Extension version: 2023.12.0
VSCodium version: VSCodium 1.79.2 (19c0f5cefaeb2637b45a9c7a356151fcfdcda1e9, 2023-06-15T18:19:23.116Z)
OS version: Linux x64 6.0.7-arch1-1
Modes:
The text was updated successfully, but these errors were encountered: