Open KungFuLucky7 opened 3 years ago
One additional side note unrelated to this issue is if there's already a .venv folder created with python3 -m venv .venv as suggested by official doc (https://docs.python.org/3/library/venv.html), it doesn't seem to recognize that virtualenv in-place and insists on creating new virtual environment in ~/.virtualenvs with mkdir. Maybe you can provide a configuration option to enable in-place virtualenv similar to poetry's configuration option.
Yep this is a known issue and one I wish I had known about in hindsight!
It might be I'll have to rename this file and provide backwards compatibility for a short period of time while users move over.
however, it doesn't seem to be able to detect virtual environment already activated properly.
Does pycharm activate the virtualenv for you automatically (I'm unfamiliar with the way pycharm works)
I can set PyCharm Python interpreter to the .venv
path and it activates the environment whenever I open a new terminal.
Issue Details
Please provide the following details when opening an issue:
Operating System (uname -a)
Mac OSX
zsh version (zsh --version)
zsh 5.8 (x86_64-apple-darwin20.0)
autoswitch-virtualenv version
3.1.1
How is zsh-autoswitch-virtualenv installed?
Steps to reproduce the issue
Every time I open up PyCharm terminal I get this verbose, prolonged error message:
zsh-autoswitch-virtualenv
is a very nice tool because it supports poetry, however, it doesn't seem to be able to detect virtual environment already activated properly.One additional side note unrelated to this issue is if there's already a
.venv
folder created withpython3 -m venv .venv
as suggested by official doc (https://docs.python.org/3/library/venv.html), it doesn't seem to recognize that virtualenv in-place and insists on creating new virtual environment in~/.virtualenvs
withmkdir
. Maybe you can provide a configuration option to enable in-place virtualenv similar to poetry's configuration option.gist link to your zshrc