python3Packages.yarg: remove nose and modernize

[pyrox0]

Description of changes

Updates the yarg derivation to remove the dependency on nose, and updates the Nix code to follow modern packaging standards. Builds and tests just fine for me.

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.

[emilazy]

It looks like upstream still claims a nose dependency in requirements-test.txt, tox.ini, and runtests.py – I guess it’s vestigal and pytest can handle the orchestration, if you’re sure that the same tests are being run as before this change?

[pyrox0]

It looks like upstream still claims a nose dependency in requirements-test.txt, tox.ini, and runtests.py – I guess it’s vestigal and pytest can handle the orchestration, if you’re sure that the same tests are being run as before this change?

yes, the same tests are still being run, using pytest's nose compatibility layer.

[emilazy]

Sounds good to me then!

[emilazy]

Looks good, thank you for sending this upstream! Sorry that I can’t merge these myself…

By the way, I only just recently learned about fetchpatch2 and #257446 – if you’re a best‐practices stickler like me then you might be interested in starting to use fetchpatch2 { url = "…?full_index=1"; } for GitHub patches. (But this is absolutely not worth holding up this PR over, given how ubiquitous fetchpatch is already.)

[pyrox0]

I'm very much a stickler for good code and best practices, updated to use fetchpatch2/full_index! I'll keep it in mind for future PRs as well, that's a good thing to know about!

[Aleksanaa]

@ofborg build python3Packages.yarg