Tracking: #356002

This was made semi-manually.

I tried building all packages I changed while I was working on the PR, and I am fairly certain they'll build fine.

The methodology was:

• Replace --replace with --replace-fail in around ~10 packages.
• Try building them
  • If the package is marked as broken or disabled on all currently supported python3 versions, I just skip it
    • I also skip if the package is not marked as broken, but still failed
  • If there is no rebuild triggered, it is probably behind an isDarwin conditional.
    • (In those cases I made sure it worked by forcing the conditional and checking manually)
• In case the substitution fails, check if it makes sense to remove it
  • In most cases, it makes sense. I check those manually to make sure it's fine to remove
  • In a the case of blivet, I opted to use --replace-quiet instead
  • For pyu2f I had to separate out a substituteInPlace into two parts
  • In some cases non-trivial changes are needed, I just skipped those
    • I put some of them in another PR: python3Packages: remove --replace in some non-trivial cases #422428
• After the 10 packages (or less if they were skipped), are deemed to build fine with the changes, git stash them, so that they don't cause rebuilds in the next iteration of 10 packages

Here's a script that only checks out the changes
to the file that the package is defined in and then builds it.
It takes a few hours to run and will generate a failed.txt file (which will hopefully be empty).

Do note that some changes are behind optional flags, so this check is not 100% thorough.

#!/usr/bin/env bash

set -eou pipefail

# put the branch name here
# or just the git revision
branch="python-replace"

changed_files=$(git diff --name-only "$branch"~ "$branch")

git co "$branch"~
git reset "$branch"~ --hard

echo "The following packages failed to build:" > ./failed.txt

for file in $changed_files; do

  stripped=${file#pkgs/development/python-modules/}

  if [[ "$stripped" == "capstone/4.nix" ]]; then
    attrname="capstone_4"
  elif [[ "$stripped" == "numpy/1.nix" ]]; then
    attrname="numpy_1"
  elif [[ "$stripped" == "django/4.nix" ]]; then
    attrname="django_4"
  elif [[ "$stripped" == "torch/source/default.nix" ]]; then
    attrname="torch"
  elif [[ "$stripped" == "pytidylib/default.nix" ]]; then
    attrname="tidylib"
  elif [[ "$stripped" == "sudachidict/default.nix" ]]; then
    attrname="sudachidict-core"
  else
    attrname=$(dirname "$stripped")
  fi

  case "$attrname" in
    "deepwave"|"mip")
      # I didn't want to wait out the long tests...
      continue
      ;;
    "bacpypes"|"bwapy"|"pytest-cram")
      # disabled for higher versions
      python_pkgs="python311Packages"
      ;;
    "blockchain"|"certipy-ad"|"dataclasses-serialization"|"gradient-utils"|\
    "gradient"|"nampa"|"nipype"|"numpy_1"|"palace"|"pyrevolve"|"update-dotdee")
      # disabled for higher versions
      python_pkgs="python312Packages"
      ;;
    *)
      python_pkgs="python313Packages"
      ;;
  esac

  to_build="$python_pkgs"."$attrname"

  # Pull in the changes for one specific file
  git checkout "$branch" -- "$file"

  echo "Building python package: $attrname"
  if ! nix-build -A "$to_build"; then
    echo "Build failed for $attrname"
    echo "$attrname" >> ./failed.txt
  fi

  git reset "$branch"~ --hard
done

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• Nixpkgs 25.11 Release Notes (or backporting 24.11 and 25.05 Nixpkgs Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
• NixOS 25.11 Release Notes (or backporting 24.11 and 25.05 NixOS Release notes)
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other contributing documentation in corresponding paths.

Add a 👍 reaction to pull requests you find important.