-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
generated with uv==0.5.18
fails to parse in uv==0.5.19
#10654
Comments
Makes sense, thanks. |
We are running into the same issue with uv 0.5.19 with both watchdog and pycryptodome as another data point Command:
|
Looks like this was already somewhat identified: https://github.com/astral-sh/uv/blob/main/crates/uv-resolver/src/lock/mod.rs#L308
|
Omitting the tag is fine — we never supported it, so uv never would’ve selected it. The problem here is just that we can’t deserialize it from an existing lockfile. |
If you delete the entry from the lockfile, it should solve the problem without any other effect (since, as Charlie said, we don't support selecting those wheels anyway). We'll see if there's a reasonable way to support deserializing unknown tags from existing lockfiles. |
I'll try to fix this now, sorry. |
Hitting this as well, broke on CI (using a python:3.12 image) as it pulled the latest uv version:
|
Can you please include the error message for my own records? |
done :) |
This works around a bug with uv 0.5.19. See astral-sh/uv#10654 (comment).
#10655 is up which fixes this; we'll have a release out once it's merged. |
Thanks for the easy workaround btw! Removing the win_ia64 wheel was quite easy. |
Thanks for confirming @sunshowers and sorry for the disruption. |
## Summary Closes #10654 (comment).
Workaround for: astral-sh/uv#10654
error:
repro:
command
rm uv.lock && pip install uv==0.5.18 && uv lock && pip install uv==0.5.19 && uv lock
running
rm uv.lock && pip install uv==0.5.19 && uv lock
is successful <=== This is the workaround (delete and regen the lockfile)The text was updated successfully, but these errors were encountered: