Skip to content

Req: Add support for pyenv and pyenv-virtualenv #313

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

Closed
the-moog opened this issue Apr 17, 2025 · 1 comment
Closed

Req: Add support for pyenv and pyenv-virtualenv #313

the-moog opened this issue Apr 17, 2025 · 1 comment

Comments

@the-moog
Copy link

the-moog commented Apr 17, 2025

Currently if a folder is opened where the environment is managed by pyenv, this extension tries to use the global env rather than the local one.
If it were to simply use the current shell's python that would just work, but it's bypassing that.

Pyenv and Pyenv-Virtualenv is a widly used and far superior environment manager.

There seems to be no way to pass the actual path to the environment (which is usually the way if bypassing pyenv itself) Pasting the path into the dialog for "Add virtualenv" does not work.

e.g. A virtual env of Python 3.13.2 for a web project might be called 3.13.2-webprj and would exist in

/home/user/.pyenv/versions/3.13.2

With 3rd party project specific modules in

/home/user/.pyenv/versions/3.13.2-webprj

ref: https://github.com/pyenv/pyenv

@karthiknadig
Copy link
Member

This is on the plan, but we are also open for community contributed extension for this.

see #79

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants