various: move toPythonApplications from by-name to avoid override weirdness

[qweered]

Following discussion in #454559 i think this is an immidiate improvement to restore override interface

• Built on platform:
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• Tested, as applicable:
  • NixOS tests in nixos/tests.
  • Package tests at passthru.tests.
  • Tests in lib/tests or pkgs/test for functions and "core" functionality.
• Ran nixpkgs-review on this PR. See nixpkgs-review usage.
• Tested basic functionality of all binary files, usually in ./result/bin/.
• Nixpkgs Release Notes
  • Package update: when the change is major or breaking.
• NixOS Release Notes
  • Module addition: when adding a new NixOS module.
  • Module update: when the change is significant.
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

---

Add a 👍 reaction to pull requests you find important.

[qweered]

cc @NixOS/nixpkgs-core

[qweered]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 473624
Commit: da832f4d819b95b58912ad5d95312b2d3e24d1c2

---

x86_64-linux

✅ 4 packages built:

• reno
• reno.dist
• sbom4python
• sbom4python.dist

[alyssais]

Seems more like something for the Python package set maintainers than the core team…

[qweered]

cc @mweinelt @natsukium as python team members for review

[mweinelt]

• TBD: e74bcd1 all-packages: move toPythonApplication packages closer to each other
• NACK: 8019b2d treewide: move almost all toPythonApplication from by-name to top-level overlay to fix override interface
  • No reason given and I don't understand what this changes
• OK: 7db157f sbom4files: add mainProgram
• OK: 226f6fd circus, reno: use python3Packages
• TODO: 5e8ee08 python3Packages.kubernetes-validate: move expression to appropriate place
  • commit message should specify the reason
• OK: 4e62e3d gfal2-util: remove unneeded overlay

[qweered]

See reason for 8019b2d in #454559 discussion and specifically #454559 (comment). This commit allows all arguments to be overriden again

[wolfgangwalther]

See reason for 8019b2d in #454559 discussion and specifically #454559 (comment). This commit allows all arguments to be overriden again

Just because a migration in one direction breaks the override interface we don't need to immediately migrate everything in the other direction. Since that override interface was not there to begin with, nobody is relying on it right now. Or in other words: The comment you referenced pointed out two problems: The removal of the existing override interface without replacement - and the fact that after the migration, there is no proper override interface for these packages. Both are problems, but only the latter is the case here, and I don't think it warrants this kind of migration right now.

[qweered]

Converting to draft until we aggree on proper solution