You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's been a while since I opened the issue, and I'm not sure if we actually want this, since it would be hard to maintain as automated tooling like nix-update wouldn't be able to update it, and it doesn't have much of a benefit unless the builds are actually failing for the package sets we are recursing into, which is just 3.13 and 3.14 currently.
Would love to hear some opinions from the python team: @mweinelt@natsukium. Should nix-init emit disabled = by default based on the python version constraints found?
Activity
eveeifyeve commentedon Feb 14, 2026
How would this work? Because I am not too sure if this is an issue to work on.
figsoda commentedon Feb 14, 2026
It would look something like this: https://github.com/NixOS/nixpkgs/blob/a67c7f6de9dddb53101ceb2157b315f9551b3ddb/pkgs/development/python-modules/paddlepaddle/default.nix#L68
Here are some more examples: https://github.com/search?q=repo%3ANixOS%2Fnixpkgs+%2Fdisabled+%3D+python[A-Z].*%2F&type=code
It's been a while since I opened the issue, and I'm not sure if we actually want this, since it would be hard to maintain as automated tooling like nix-update wouldn't be able to update it, and it doesn't have much of a benefit unless the builds are actually failing for the package sets we are recursing into, which is just 3.13 and 3.14 currently.
Would love to hear some opinions from the python team: @mweinelt @natsukium. Should nix-init emit
disabled =by default based on the python version constraints found?