Poetry ignores `pyenv` local Python when "Python Environments" VS Code extension is active

[enricostragiotti]

Description

When the Python Environments extension in VS Code is active, poetry install does not respect the Python version set by pyenv local. Instead, it defaults to the version of Python that was used to install Poetry itself.

Steps to reproduce

1. Activate the Python Environments extension in VS Code.
2. In a project folder, run:

   pyenv local 3.13.5
   poetry install
   poetry env info

   It shows the Python version used to install Poetry, not the pyenv local version.
3. Disable the Python Environments extension and repeat the steps. Poetry now correctly uses the pyenv local Python.

Environment

Windows 11
pyenv-win 3.x
Poetry 2.x (installed with pipx)
VS Code with Python Environments extension

Let me know if you can reproduce the issue!

[eleanorjboyd]

will investigate- thanks!

[eleanorjboyd]

what is the pyproject.toml file you have in your folder in order to run poetry install?

[enricostragiotti]

Here it is!

[github-actions]

Hey @eleanorjboyd, this issue might need further attention.

@enricostragiotti, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[github-actions]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

Happy Coding!

[enricostragiotti]

@eleanorjboyd All the infos are in the toml that I have sent you, please tell me if there is something missing. Otherwise, I don't see why we should close the issue

[eleanorjboyd]

Hi! I was able to repro this issue once, but then no longer after that which is very interesting. The only thing I would think can impact the terminal (since you are just running it from there) that comes from the environments extension would be an edit to the path variable. Can you check the $PATH var and see if you see any differences? Additionally, could you try "terminal.integrated.shellIntegration.enabled": false and see if that changes it?

[eleanorjboyd]

@anthonykim1 curious on your thoughts