Poetry does not set the path for or activate the virtual environment if the active python version differs from that used to install poetry #6978

doolio · 2022-11-05T18:48:04Z

doolio
Nov 5, 2022

There have been many similar issues reported so asking here first rather than raising an issue unnecessarily. It is likely a misunderstanding/misuse on my part.

Firstly, I'm using:

asdf a CLI tool that can manage multiple language runtime versions on a per-project basis, extendable via plugins +
a. asdf-python an asdf plugin to manage python versions on a per-project basis (uses pyenv under the hood) +
poetry.

I'm running Debian 11 (Bullseye, stable):

$ which asdf
asdf is /home/doolio/.local/share/asdf/bin/asdf
$ asdf --version
v0.10.2-7e7a1fa
$ asdf plugin-list
python
$ which poetry
poetry is /home/doolio/.local/bin/poetry
$ poetry --version
Poetry (version 1.2.2)

My system python is 3.9.2 and I've installed 3.10.7 and 3.11.0 with asdf.

$ which python
bash: type: python: not found
$ which python3
python3 is aliased to `python3 -q'
python3 is /usr/bin/python3
python3 is /bin/python3
$ python3 --version
Python 3.9.2
$ asdf list
python
  3.10.7
  3.11.0

My poetry config is as follows:

$ poetry config --list
cache-dir = "/home/doolio/.cache/pypoetry"
experimental.new-installer = true
experimental.system-git-client = false
installer.max-workers = null
installer.no-binary = null
installer.parallel = true
virtualenvs.create = true
virtualenvs.in-project = null
virtualenvs.options.always-copy = false
virtualenvs.options.no-pip = false
virtualenvs.options.no-setuptools = false
virtualenvs.options.system-site-packages = false
virtualenvs.path = "{cache-dir}/virtualenvs"  # /home/doolio/.cache/pypoetry/virtualenvs
virtualenvs.prefer-active-python = true
virtualenvs.prompt = "{project_name}-py{python_version}"

Now Python 3.10.7 was active when I installed poetry with the official installer. My issue is if I set any of the other python versions to be the active version poetry creates the virtual environment using the active python since virtualenvs.prefer-active-python = true (good) but it does not set the path to the virtual environment nor activate it. See below.

Workflow:

poetry new --src demo-project
cd demo-project
asdf local python 3.11.0 ... this sets the active python to Python 3.11.0
poetry install

$ asdf current python
python          3.11.0          /home/doolio/projects/learning/python/demo-project/.tool-versions
$ python3 --version
Python 3.11.0
$ poetry env list --full-path
/home/doolio/.cache/pypoetry/virtualenvs/demo-project-k8-nqTjx-py3.11
$ poetry debug info

Poetry
Version: 1.2.2
Python:  3.10.7

Virtualenv
Python:         3.10.7
Implementation: CPython
Path:           NA
Executable:     NA

System
Platform:   linux
OS:         posix
Python:     3.10.7
Path:       /home/doolio/.local/share/asdf/installs/python/3.10.7
Executable: /home/doolio/.local/share/asdf/installs/python/3.10.7/bin/python3.10

As you can see the Path and Executable are not set within the virtual environment. Also, the Valid field is missing but perhaps expected if the other fields are not set. The other information is also incorrect. It suggests the python version inside the virtual environment is 3.10.7 but it is actually 3.11.0 as I want. For the system python I'm unsure why it suggests it is 3.10.7. I would expect it to be either 3.9.2 the true system version or 3.11.0 to indicate the active python on the system in this case.

It does however do this if the active python version is the same as the one used to install poetry. From this I take it the system version indicates the currently active version of python on the system.

$ asdf current python
python          3.10.7          /home/doolio/projects/learning/python/demo-project2/.tool-versions
$ python3 --version
Python 3.10.7
$ poetry env list --full-path
/home/doolio/.cache/pypoetry/virtualenvs/demo-project2-NDxczNWq-py3.10 (Activated)
$ poetry debug info

Poetry
Version: 1.2.2
Python:  3.10.7

Virtualenv
Python:         3.10.7
Implementation: CPython
Path:           /home/doolio/.cache/pypoetry/virtualenvs/demo-project2-NDxczNWq-py3.10
Executable:     /home/doolio/.cache/pypoetry/virtualenvs/demo-project2-NDxczNWq-py3.10/bin/python
Valid:          True

System
Platform:   linux
OS:         posix
Python:     3.10.7
Path:       /home/doolio/.local/share/asdf/installs/python/3.10.7
Executable: /home/doolio/.local/share/asdf/installs/python/3.10.7/bin/python3.10

Is this a bug or a misunderstanding/misuse by me?

Thanks for your time and this package.

doolio · 2022-11-05T18:54:05Z

doolio
Nov 5, 2022
Author

Seems to be the same as issue #6893 which I didn't see before.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Poetry

Poetry does not set the path for or activate the virtual environment if the active python version differs from that used to install poetry #6978

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Poetry

Poetry does not set the path for or activate the virtual environment if the active python version differs from that used to install poetry #6978

Uh oh!

doolio Nov 5, 2022

Replies: 1 comment

Uh oh!

doolio Nov 5, 2022 Author

doolio
Nov 5, 2022

doolio
Nov 5, 2022
Author