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
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
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
With 3rd party project specific modules in
ref: https://github.com/pyenv/pyenv
The text was updated successfully, but these errors were encountered: