-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Closed
Labels
kind/bugSomething isn't working as expectedSomething isn't working as expectedstatus/triageThis issue needs to be triagedThis issue needs to be triaged
Description
- I am on the latest Poetry version.
- I have searched the issues of this repo and believe that this is not a duplicate.
- If an exception occurs when executing a command, I executed it again in debug mode (
-vvvoption).
- OS version and name: Linux nef-devel 3.10.0-693.17.1.el7.x86_64 # 1 SMP Thu Jan 25 20:13:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
- Poetry version: 1.1.14
- Link of a Gist with the contents of your pyproject.toml file:
https://gist.github.com/cifkao/cf3e0b23bc075bda6700400c3b1bebfc
Issue
I have a project that requires Python ^3.9. The system installation in /usr/bin/python3 is Python 3.6 and I'm in a Conda environment with Python 3.9.7.
Running poetry install gives:
The currently activated Python version 3.6.8 is not supported by the project (^3.9).
Trying to find and use a compatible version.
Using python3 (3.9.7)
Creating virtualenv poetry-test-PDOMCCYP-py3.9 in /home/ocifka/.cache/pypoetry/virtualenvs
Updating dependencies
Resolving dependencies... (0.1s)
Writing lock file
However, this is the opposite of what happens.
Firstly, the activated Python was version 3.9.7 (from Conda) and not 3.6.8:
$ python --version
Python 3.9.7
Secondly, Poetry goes ahead and installs Python 3.6.8:
$ ~/.cache/pypoetry/virtualenvs/poetry-test-PDOMCCYP-py3.9/bin/python --version
Python 3.6.8
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/bugSomething isn't working as expectedSomething isn't working as expectedstatus/triageThis issue needs to be triagedThis issue needs to be triaged