-
-
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
Python: change bootstrapping. #248866
Python: change bootstrapping. #248866
Conversation
I have rebased this on staging-next for now to make it a little easier to reason about for me. I propose:
|
866cd47
to
fbed5e9
Compare
I'm going to start one more run. I'm pretty confident we can merge then. Please don't add any more unrelated updates, only (larger) fixes. |
jedi has one failing test on all platforms which has to be resolved |
|
The last 3 commits are PRs that were either merged or are targeting |
After that we can trigger hydra again. |
Small scipy update at #249921 . |
About 4000 failures on this branch. |
I looked through a good number of the failures and listed them at the top of #247287. The biggest improvement will be from fixing |
installShellCompletion --cmd pip \ | ||
--bash <($out/bin/pip completion --bash) \ | ||
--fish <($out/bin/pip completion --fish) \ | ||
--zsh <($out/bin/pip completion --zsh) |
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.
<($out/bin/pip completion --zsh --no-cache-dir)
will properly clear the warning about .cache/pip
not being writable. zsh may not work until pypa/pip#12166 is closed. (given pip is at the bottom of ~40000 packages leaving it in seems fine)
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.
Also fixes #224610
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.
Thank you for figuring that out. This was merged without that change, but we should add this in a separate commit.
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.
Please do. I'm working on another change atm and don't need the two things coupled.
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.
Tacked it on to this change https://github.com/NixOS/nixpkgs/pull/250398/files
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.
Thank you, I appreciate you creating that PR. I'm sorry I hadn't found the time yet today.
After #248866, we have stronger build-time dependency validation This fixes "ERROR: Missing dependencies: ninja"
sed -i "/versioningit >=/d" pyproject.toml | ||
sed -i '/^name =.*/a version = "${version}"' pyproject.toml | ||
sed -i "/dynamic =/d" pyproject.toml |
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.
nit: those could have been combined into one command
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.
Yes, you're right. At the same time, even though it's less efficient, I feel that keeping separate commands here is more readable. But this motivates me to look into whether we can handle versioningit better in general, thank you!
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 always find less code overhault more readable unless you are using some special character shortcuts. Like here, eg deduplicating pyproject.toml but as said it is not that super important and focusing on getting a setup-hook for verioningit is a better solution anyway.
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/psa-poetry2nix-is-currently-broken-with-nixpkgs-unstable/32281/1 |
In NixOS/nixpkgs#248866, `pip` stopped getting included by default when building packages.
Should we backport this to 23.05? I'm seeing errors on 23.05 because some inconsistency happened:
And 23.05 is still using the old wheel package:
|
I don't think it fits backporting criteria, also 23.11 is imminent |
Description of changes
This is #245509 but then on
python-updates
branch so we can use Hydra.Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)