forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Closed
Copy link
Labels
area-environmentsFeatures relating to handling interpreter environmentsFeatures relating to handling interpreter environmentsbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugmacosneeds PRReady to be worked onReady to be worked onregressionBug didn't exist in a previous releaseBug didn't exist in a previous release
Description
Environment data
- VS Code version: 1.57.0-insider 37a12c9
- Extension version (available under the Extensions sidebar): v2021.5.829140558
- OS and version: macOS 11.4
- Python version (& distribution if applicable, e.g. Anaconda): pyenv
- Type of virtual environment used (N/A | venv | virtualenv | conda | ...): pyenv
- Relevant/affected Python packages and their versions: all
- Relevant/affected Python-related VS Code extensions and their versions: all
- Value of the
python.languageServersetting: Pylance
[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
Interpreter shows all pyenv base versions and virtual environments.
Actual behaviour
When I open the interpreter to select a Python version it shows all the virtual environment I have created in pyenv from the different base version, but not the base versions themselves. That is, I can select a virtual environment XXX based on 3.7.6 but not 3.7.6 itself.
yoda-vid, mart-r, griels, gvandermerwe-r7, MagnusOxlund and 3 more
Metadata
Metadata
Assignees
Labels
area-environmentsFeatures relating to handling interpreter environmentsFeatures relating to handling interpreter environmentsbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugmacosneeds PRReady to be worked onReady to be worked onregressionBug didn't exist in a previous releaseBug didn't exist in a previous release