question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Interpreter does not show base pyenv versions when the env dirs are symbolic links

See original GitHub issue

Environment data

  • VS Code version: 1.57.0-insider 37a12c9b0846167b2f68e9e1f276149d2d8b9b27
  • 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.languageServer setting: 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.

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:1
  • Comments:24

github_iconTop GitHub Comments

1reaction
albireoxcommented, Sep 2, 2021

I don’t think the python binary (or the link to it) shows up in the root of the pyenv version. I think it’s supposed to be inside bin/. It’s the same with the virtual environments that do show up for me in VSCode.

$ ls /Users/albireo/.pyenv/versions/archon/
total 4.0K
drwxr-xr-x 95 albireo staff 3.0K Aug 22 21:33 bin/
drwxr-xr-x  2 albireo staff   64 Apr  5 08:53 include/
drwxr-xr-x  3 albireo staff   96 Apr  5 08:53 lib/
-rw-r--r--  1 albireo staff  131 Apr  5 08:53 pyvenv.cfg
drwxr-xr-x  3 albireo staff   96 Apr  5 10:12 share/
0reactions
albireoxcommented, May 13, 2022

Pinging again about this. As far as I can see it’s still happening.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Cannot add symlinked Python/virtualenv as interpreter, e.g. ...
I "solved" it by using the PyCharm dialog "Create VirtualEnv". In the new virtualenv, /bin/python is not an "alias"/symlink to /Library/Frameworks/Python.
Read more >
Why is virtualenv creating symlinks to my primary python ...
My understanding (which may be erroneous) is that the interpreter is housed in the bin folder. Am I wrong, and the lib and...
Read more >
venv — Creation of virtual environments — Python 3.11.1 ...
Running this command creates the target directory (creating any parent directories that don't exist already) and places a pyvenv.cfg file in it with...
Read more >
Pyenv and Pipenv (on MacOS) – Index - Wilson Mar
On a MacOS Catalina version operating system, you would see: ... but is not symlinked into /usr/local Could not symlink bin/pkg-config ...
Read more >
How to Install and Manage Multiple Python Versions on Mac
Pyenv is a program that's used for Python version management on macOS and ... minor, and micro versions but it doesn't include alpha,...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found