python3Packages.kmapper: fix tests

[dotlambda]

Motivation for this change

ZHF: #122042

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Ensured that relevant documentation is up to date
• Fits CONTRIBUTING.md.

[jonringer]

I should have fixed this on staging.... https://github.com/NixOS/nixpkgs/pull/121639/files

[dotlambda]

We can still merge this. It uses pytestCheckHook and shouldn't create a merge conflict.

[r-rmcgibbo]

Result of nixpkgs-review pr 122088 at 342a8db run on aarch64-linux 1

3 packages built successfully:

• python38Packages.kmapper
• python38Packages.scikit-tda
• python39Packages.kmapper

---

Result of nixpkgs-review pr 122088 at 342a8db run on x86_64-linux 1

1 package failed to build:

• python39Packages.kmapper

1 package skipped due to time constraints:

• python38Packages.scikit-tda

1 package built successfully:

• python38Packages.kmapper

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

[jonringer]

We can still merge this. It uses pytestCheckHook and shouldn't create a merge conflict.

Ironically, my thoughts exactly 😁