Revert "python312Packages.numba: use a single numpy version; don't propagate it"

[dotlambda]

Description of changes

This reverts commit 3bad188.
Numba doesn't work without NumPy and it's in upstream's setup_requires as well as install_requires.

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.11 Release Notes (or backporting 23.11 and 24.05 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.

[natsukium]

That PR also removed numpy from build-system.

[doronbehar]

I'm sorry but I don't agree with this policy. If there was a single numpy version in all of python3.pkgs, we wouldn't have argued so much. If you'd be able to iterate all usages of numpy_1 and make sure that there are no breakages when that is upgraded to numpy_2, I will let it go.

[dotlambda]

If there was a single numpy version in all of python3.pkgs

There is, at least once this PR is merged. Every Python package uses numpy rather than numpy_2.

If you'd be able to iterate all usages of numpy_1 and make sure that there are no breakages when that is upgraded to numpy_2, I will let it go.

I already showed you how you'd make sure of that: #327446 (comment)

@doronbehar Honestly, you're not engaging with my proposed solutions so I don't see why I should keep arguing against your non-solution.
But again, it's a non-solution because as of right now, python3.withPackages (ps: [ ps.numba ]) is broken:

$ python3 -c "import numba"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/nix/store/w5af1gfflkph66mrghmqdhvxspz2dl7y-python3-3.12.5-env/lib/python3.12/site-packages/numba/__init__.py", line 54, in <module>
    _ensure_critical_deps()
  File "/nix/store/w5af1gfflkph66mrghmqdhvxspz2dl7y-python3-3.12.5-env/lib/python3.12/site-packages/numba/__init__.py", line 34, in _ensure_critical_deps
    import numpy as np
ModuleNotFoundError: No module named 'numpy'

The Python maintainers disagree.