-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Venv not detected correctly #21619
Comments
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! |
Closing in favor of #1479 |
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: