python3Packages.pytest-cov-stub: init at 1.0.0

[pbsds]

Description of changes

#327220 (comment) finally inspired me to implement this idea I've been brewing for quite a while: a pytest-cov stub that does nothing but accept the command line options and provide empty no-op fixtures.

follow-up candidates for stubbing:

• pytest-pylint
• pytest-pycodestyle

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.

[pbsbot]

Result of nixpkgs-review pr 328550 run on x86_64-linux 1

20 packages built:

• python311Packages.birch
• python311Packages.birch.dist
• python311Packages.cachier
• python311Packages.cachier.dist
• python311Packages.pytest-cov-stub
• python311Packages.pytest-cov-stub.dist
• python311Packages.strct
• python311Packages.strct.dist
• python312Packages.birch
• python312Packages.birch.dist
• python312Packages.cachier
• python312Packages.cachier.dist
• python312Packages.pytest-cov-stub
• python312Packages.pytest-cov-stub.dist
• python312Packages.strct
• python312Packages.strct.dist
• remote-exec
• remote-exec.dist
• todoman
• todoman.dist

[emilazy]

Interesting. Seems like a reasonable enough approach. Is pytest-cov really so slow that it’s worth the effort to stub this out? Or is it a matter of avoiding spurious failures?

[pbsds]

coverage testing is a developer sanity test, not neccesarily a correctness test. It should not block distribution and common practice in nixpkgs is to patch it out, as shown in some of the examples in this PR.

EDIT: also it puts the interpreter in a mode where it records all lines executed, which greatly slows down the test suite.

[pbsds]

I pushed a change that re-implements the stubs rather than wrap the ones from pytest-cov, which will save a lot of rebuilds

[pbsbot]

Result of nixpkgs-review pr 328550 run on x86_64-linux 1

20 packages built:

• python311Packages.birch
• python311Packages.birch.dist
• python311Packages.cachier
• python311Packages.cachier.dist
• python311Packages.pytest-cov-stub
• python311Packages.pytest-cov-stub.dist
• python311Packages.strct
• python311Packages.strct.dist
• python312Packages.birch
• python312Packages.birch.dist
• python312Packages.cachier
• python312Packages.cachier.dist
• python312Packages.pytest-cov-stub
• python312Packages.pytest-cov-stub.dist
• python312Packages.strct
• python312Packages.strct.dist
• remote-exec
• remote-exec.dist
• todoman
• todoman.dist

[pbsds]

@ofborg build python311Packages.pytest-cov-stub python312Packages.pytest-cov-stub

[github-actions]

Successfully created backport PR for release-24.05:

• [Backport release-24.05] python3Packages.pytest-cov-stub: init at 1.0.0 #331129