[staging-next] python311Packages.scikit-learn: 1.3.2 -> 1.4.0

[bryango]

Description of changes

Fix pytest failure: https://hydra.nixos.org/build/247211840/nixlog/1 since: #282506.
This may or may not fix many downstream packages in staging-next.
See upstream scikit-learn/scikit-learn#27628 for details.

Changelog: https://scikit-learn.org/stable/whats_new/v1.4.html

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/)
• 24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (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.

---

Add a 👍 reaction to pull requests you find important.

[vcunat]

Sounds OK to me, though I don't know this package in particular. The ChangeLog shows lots of API changes, but I think that's relatively common for python packages.

[bryango]

I also do not understand the full repercussions of this version bump... Maybe some python expert should take a look? 😉 I failed to nixpkgs-review it as the change seems to be too large for my laptop...

Update: I went through the changelog and the number of API changes is terrifying. I am okay for this to be closed if we decided that it is too soon for a version bump. One can simply disable the test_singular_matrix to fix the build for now.

@ofborg eval

[vcunat]

Let me merge this PR as is, so that the build is fixed at least. Further improvements can be done later.