poetry and pyenv don't work well together

I am using pyenv to manage my python versions and virtualenvs. This seems to cause some problems with poetry.

>> which python
~/.pyenv/shims/python
>> which pip
~/.pyenv/shims/pip
>> poetry run which python
~/.cache/pypoetry/virtualenvs/XXXXX-py3.6/bin/python
>> poetry run which pip
~/.pyenv/shims/pip

This seems to cause the issue, that packages are installed in to the python version set by pyenv, but the python interpreter is used from the poetry virtualenv. This is no problem, when I activate the virtualenv first and then run poetry install But if I want to rely on poetry’s automatic virtualenv management, this doesn’t work anymore.

If you need more info I’ll gladly provide it.

Thanks for your great work and tool, it’s a real pleasure to work with 😃

[sdispater]

I am currently using pyenv on MacOS and I don’t have any problem making it working.

I didn’t do anything special, I only have this on my .zshrc:

# pyenv
export PYENV_ROOT=/usr/local/var/pyenv

if [[ -z "$VIRTUAL_ENV" ]]; then
    eval "$(pyenv init -)"
    eval "$(pyenv virtualenv-init -)"
fi

[anpr]

Just to give my feedback here, I’m new to poetry and encountered issues when using pyenv and poetry together. Basically, it installed packages to a newly created virtualenv directory that was then nowhere to be found, poetry shell didn’t work, etc.

I installed poetry using curl -sSL https://raw.githubusercontent.com/sdispater/poetry/master/get-poetry.py | python. My python used there is python 3.7.1 from ~/.pyenv/shims/python. Then I went to my code repository, activated my pyenv virtualenv, executed poetry install and had the problems mentioned above.

I’m just commenting here, because I believe there is some underlying issue here that’s not fixed.