-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Poetry doesn't find a compatible version of python, even though one is available #7772
Comments
poetry isn't simply inventing perhaps you have copied an unwanted Anyway, if you can't figure it out yourself and are hoping that someone else will help - please provide a way to reproduce the issue. |
Hm, I made the assumption that 3.11 was recorded in the lock file somewhere, but I just made a minimal reproduction and that's definitely not the case so I'm really not sure where it's coming from. Here's what I have to reproduce: pyproject.toml
Dockerfile
'pip list' there isn't special. I was originally getting it with a different, more useful pip command there. Running
while running |
The issue is avoided by adding the line |
So the issue is:
And we are catching |
this is fixed in #7771 (by first doing |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
-vvv
option) and have included the output below.Running with
-vvv
did not produce additional output.Issue
In my project, I have the python dependency
python = "~=3.10"
. I happen to have python 3.11 available on my development laptop, so I use that there. As part of our build pipeline, the pyproject.toml and poetry.lock files are copied into a Debian docker image which has a default python of 3.7, and has 3.10 but not 3.11 available. Prior to Poetry 1.4.0 this worked fine - Poetry would note that 3.7 wasn't supported by the project and then discover and use 3.10 automatically:On Poetry 1.4.0 and higher, that doesn't happen. Instead, I get an error because 3.11 isn't available:
I believe this behavior was introduced by #7221 , although I haven't read through the associated MR in detail yet.
The text was updated successfully, but these errors were encountered: