-
-
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
python3Packages: Fix and document the removal of the local .overrideAttrs
attribute
#350127
python3Packages: Fix and document the removal of the local .overrideAttrs
attribute
#350127
Conversation
|
The change fixes the eval failures for that attribute for me. Thank you! But I'm afraid I found another eval failure:
It bisects down to the same 58bfe74 |
…ge { ... }).overrideDerivation Clean up the leftover of commit 58bfe74 ("buildPython*: Deprecate and remove (buildPython* { ... }).override")
…Derivation Use lib.overrideDerivation instead of <pkg>.overrideDerivation to fix the evaluation of python3Packages.pythonCatchConflictsHook.tests.catches-conflict-multiple-chains, as buildPythonPackage and buildPythonApplication no longer provide <pkg>.overrideDerivation Clean up the leftover of commit 58bfe74 ("buildPython*: Deprecate and remove (buildPython* { ... }).override")
@trofi I'll fix it as well. Would you mind sharing how you found those evaluation errors in |
a57edf0
to
296d1fd
Compare
buildPythonPackage no longer provide local .override attribute. Use overridePythonAttrs instead.
296d1fd
to
38e7722
Compare
I'm using this script: https://github.com/trofi/nixpkgs-overlays/blob/main/lib/all-attrs-iter.bash and run it as:
|
Tested the attribute evaluation against the current branch state. All good now. Thank you! |
@trofi, could you officially approve this PR using the GitHub Review? This would make the approval more visible. |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/prs-already-reviewed/2617/2063 |
As the Nixpkgs 24.11 branch-off is made, this PR should be backported onto the |
Cc: @natsukagami |
Oops! Sorry for bothering and thank you for the redirection. |
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.
Sorry for the missing. LGTM, thanks.
Successfully created backport PR for |
Git push to origin failed for release-24.11 with exitcode 1 |
This PR cleans up the leftover of #333670.
After #333670,
buildPythonPackage
andbuildPythonApplication
no longer applylib.makeOverridable
themselves and no longer provide.override
and.overrideDerivation
of the returning package.For Python packages provided by Nixpkgs, the local
.override
attribute is almost always shadowed by the one provided bycallPackage
, and so does the.overrideDerivation
attribute. I didn't find any use of the localoverride
in Nixpkgs, but @trofi reported the evaluation failure ofpython3Packages.pythonCatchConflictsHook.tests.catches-conflict-multiple-chains
due to the loss of the localoverrideDerivation
.This PR uses
lib.overrideDerivation
instead of theoverrideDerivation
attribute to fix the evaluation ofpython3Packages.pythonCatchConflictsHook.tests.catches-conflict-multiple-chains
and document the removal of thebuildPython*
-generated localoverrideDerivation
attribute in the release note.Update: As the Nixpkgs 24.11 branch-off is made, this PR should be backported onto the
release-24.11
branch once it is merged.Things done
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.