-
Notifications
You must be signed in to change notification settings - Fork 15
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 checks no longer work #138
Comments
Overlays no longer appear to affect `buildPythonPackage` since NixOS/nixpkgs@33d12e5 Disable the positive tests until that is resolved. See: #138
Hi @jtojnar is this still relevant today? |
@AkechiShiro Yes, I have not found the time to fix this yet. |
How can I help investigate/fix this, it looks a bit complicated due to the nature of the change that was made upstream ? What do you recommend me to do so I can dig into this and help you maybe get closer to fix it, I don't know if I'll be able to as this is my first contribution to this nix community project. |
You can clone It does not matter if it is your contribution but it will be pretty hard so it depends on how you are proficient with Nix or comfortable reading the overlay and fix-point heavy Nix code for stdenv and Python packaging. |
Fine, thanks for the detailed instructions @jtojnar, let me take up this challenge, if I fail, I'll only have learned more, no one can fix everything on their first tries. |
The overlay produced by
checkBuildPythonPackageFor
no longer appears to overridebuildPythonPackage
:nixpkgs-hammering/lib/default.nix
Lines 83 to 111 in 54411aa
And the one from
checkFor
does not seem to apply tomkDerivation
used bybuildPythonPackage
internally (even though it works for packages usingstdenv.mkDerivation
directly:nixpkgs-hammering/lib/default.nix
Lines 69 to 76 in 54411aa
I bisected the breakage to NixOS/nixpkgs@33d12e5
The text was updated successfully, but these errors were encountered: