-
-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Open
adisbladis
wants to merge
11
commits into
NixOS:master
Choose a base branch
from
adisbladis:uv-update-no-staging
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
uv: 0.4.30 -> 0.5.8 #367280
+49
−6,101
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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]>
adisbladis
force-pushed
the
uv-update-no-staging
branch
from
December 22, 2024 03:37
7be0736
to
00ce0da
Compare
MisileLab
approved these changes
Dec 22, 2024
I targeted |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.