poetry shell does not activate virtualenv

• I am on the latest Poetry version.
• I have searched the issues of this repo and believe that this is not a duplicate.

• OS version and name: Mac OS X, High Sierra
• Poetry version: 0.12.5

Issue

Similar to pipenv shell, I would have expected that when running poetry shell the virtualenv gets activated, but apparently this is not the case…

➜ which python
/Users/timon/.pyenv/shims/python
➜ poetry shell
Spawning shell within /Users/timon/Library/Caches/pypoetry/virtualenvs/YOLO-SAR-py3.7
➜ which python
/Users/timon/.pyenv/shims/python
➜ source /Users/timon/Library/Caches/pypoetry/virtualenvs/yolo-sar-py3.7/bin/activate
➜ which python
/Users/timon/Library/Caches/pypoetry/virtualenvs/yolo-sar-py3.7/bin/python

for comparison

➜ poetry run which python
/Users/timon/Library/Caches/pypoetry/virtualenvs/yolo-sar-py3.7/bin/python

Am I misunderstanding something and this is expected behaviour or is it a bug?

Thanks a lot already for your time 😃

[betafcc]

Just in case someone else came googling for a quick but reliable temporary alternative that works in all shells:

# on .{bash,zsh,wtv}rc
alias poetry_shell='. "$(dirname $(poetry run which python))/activate"'

[wfa207]

tl; dr — Move your pyenv and poetry configuration settings to ~/.bash_profile (make sure poetry configs come after pyenv’s) and out of ~/.bashrc if you’re using bash.

I got stuck on this issue in bash and the main issues seem to stem from the interaction of pyenv and poetry’s PATH-setting configuration found in my dotfiles:

# Initialize pyenv when a new shell spawns
eval "$(pyenv init -)"

# Modify path for Python's poetry dependency management system
export PATH="$HOME/.poetry/bin:$PATH"

I found that moving these scripts to ~/.bash_profile (as opposed to ~/.bashrc) helps resolve this issue. The problem in bash stems from the fact that ~/.bash_profile gets executed only on login (OS X registers new windows / panes as logins), whereas ~/.bashrc gets executed each time a shell is started. Because poetry shell is running a bash shell under the hood, it will also source ~/.bashrc (and therefore the pyenv script) when it is run, thus prepending pyenv’s shims to PATH after the virtual env is activated. By moving these configuration settings to ~/.bash_profile, we avoid this issue and the virtual env can prepend its path to PATH unfettered.