-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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: 0.4.30 -> 0.5.8 #367280
uv: 0.4.30 -> 0.5.8 #367280
Conversation
Signed-off-by: misilelab <[email protected]>
Signed-off-by: misilelaboratory <[email protected]>
Using `buildPythonPackage` triggers dependency propagation, meaning that using `uv` with `nix-shell` results in a a shell with the `uv` Python input in it. This is problematic for development usage where you only want the one specified version. Often this design bug in the Python package builders is worked around by deleting `$out/nix-support/propagated-build-inputs`, but since `uv` is written in Rust and can be built without a Python interpreter so it's better to just build without a Python interpreter.
This fixes cross builds
Signed-off-by: misilelaboratory <[email protected]>
Signed-off-by: misilelab <[email protected]>
Signed-off-by: misilelab <[email protected]>
7be0736
to
00ce0da
Compare
I targeted |
@@ -47,29 +38,32 @@ python3Packages.buildPythonApplication rec { | |||
"uv" | |||
]; | |||
|
|||
postInstall = '' | |||
# Tests require python3 | |||
doCheck = false; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
checkInputs?
Yes this was the reason. I also agree to target |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this PR is worth merging.
staging-next
is expected to be merged either today or tomorrow.
#361878 has been merged in |
Things done
This cherry picks changes done to
uv
on staging.Uv updates should never have started going to staging and now that decision keeps leaking in to the
uv
update workflow.The motivation here is to stop using the staging workflow for uv and go straight to master.
The relatively large rebuild count of
uv
is caused by a home-assistant test setup hack, and not a reason to keep targeting staging.See related links for more discussion/complaints:
Note: While 0.5.11 is the latest release 0.5.8 is the latest release that supports rustc <1.83.
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.