-
Notifications
You must be signed in to change notification settings - Fork 1.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
uv lock
creates a lockfile that can't be installed
#12241
Comments
There's a fairly thorough write-up on this problem here: https://docs.astral.sh/uv/concepts/resolution/#required-environments |
Thanks!
(Not sure why, I believe they should be correct.) But eventually it worked with this argument:
|
Actually, it just builds the same lock file, but adds a section for win_64 with |
I don't think we look at |
I'm sorry for wasting your time with stupid stuff. My company blocks pypi, we have our "internal pypi" which has some bogus security scanner that blocks certain versions. |
That's ok, I understand. Let me re-open. |
Question
Basic question
My
pyproject.toml
specifiespython >= 3.11
.My actual
.venv
has python 3.12.When I run
uv lock
, it creates a lockfile that works for python 3.11, but fails for python 3.12.Is this the intended behavior?
Specific details
My company has our own internal pypi index. It has some oddities.
For example,
numpy==2.2.4
is available for python 3.11, but not yet available for newer versions of python.If I run
uv lock
, it creates a lockfile that specifiesnumpy==2.2.4
.If
uv
chosenumpy==2.2.3
instead, it would be installable on3.11, 3.12, 3.13
.Why I'm confused.
The
uv.lock
file lists various wheels forpython 3.11, 3.12, 3.13
, so it seems to be trying to build a lockfile that works for those three versions. But the lockfile it eventually produces can't be installed on any version except3.11
.Platform
No response
Version
No response
The text was updated successfully, but these errors were encountered: