virtualenvwrapper.plugin.zsh does not support tmux and pyenv together

[oscargicast]

Hi,

I started using pyenv with pyenv-virtualenvwrapper an it works like a sharm with this plugin.

The problem comes when I try to use tmux. For example, when I run this:

$ tmux new -s session_name

I get [exited] as response:

I realized this line in the plugin makes tmux exits automatically:

source ${${virtualenvwrapper}:c}

I could start tmux in my zsh config file. Despite that, I can not start any other session so the usage of tmuxinator, for instance, is not possible :(

I really appreciate your help. This is a link with of my dotfiles.

Thanks.

[ckt114]

Had the same issue. Had to remove virtualenvwrapper from plugins to be able to use pyenv.

[propyless]

Old issue, but I had this problem today and turns out it was due to asdf which I use to manage different python version. The shims it creates wrappers for the binaries found in the python installations bin folder. So the shim looks like so.. and can't be sourced.

I just modified the oh-my-zsh virutalenvwrapper plugin with the paths to the actual virtualenvwrapper.sh script and that resolved the issue for me.

#!/usr/bin/env bash
# asdf-plugin: python 3.6.8
exec /home/propyless/.asdf/bin/asdf exec "virtualenvwrapper.sh" "$@"

Not sure if you have the same issue still today/using asdf or something similar, but this was the cause for me :)

I don't use pyenv, but the problem might be similar with the shims?

[awgymer]

I think I may be having a similar issue. I am running on Mac Catalina 10.15.2.

I have installed pyenv via homebrew and then I used pip to install virtualenvwrapper using my pyenv python 3.8.2. I do not have pyenv-virtualenv or pyenv-virtualenvwrapper installed.

When I added virtualenvwrapper to my plugins like so plugins=(git pyenv virtualenvwrapper) it caused my terminal to hang for a long time before giving me this:

Last login: Fri Apr 10 12:52:29 on ttys001
[Process completed]

[mcornella]

The virtualenvwrapper plugin has significantly changed. Please open a new issue if this is still happening.