pythonPackages.pyschedule: init at 0.2.34

[costrouc]

closes PR #37371. That PR was inactive

Motivation for this change

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Assured whether relevant documentation is up to date
• Fits CONTRIBUTING.md.

---

[worldofpeace]

Builds for all interpreters, but I didn't see any tests being ran in the output.
None in the tarball either.

[costrouc]

@worldofpeace just checked and added a note that the tests are not included with the release. https://github.com/timnon/pyschedule/tree/master/examples

[costrouc]

@GrahamcOfBorg build python2Packages.pyschedule python3Packages.pyschedule

[worldofpeace]

@worldofpeace just checked and added a note that the tests are not included with the release. https://github.com/timnon/pyschedule/tree/master/examples

Thanks. It's also a good idea to try to convince the author to distribute tests because they're useful to many distros.

[costrouc]

On that note. Yes I've run into this many times. I'll have to have a message that I can paste as an issue for the project when I run into this.

[worldofpeace]

On that note. Yes I've run into this many times. I'll have to have a message that I can paste as an issue for the project when I run into this.

Exactly, pretty much an explanation we can all agree on.
This looks paste-able from dotlambda

• Include tests in PyPI tarball clarete/forbiddenfruit#23

Web search for reference

• https://duckduckgo.com/?q=dotlambda+site%3Agithub.com+Include+tests+in+PyPi+tarball&t=h_&ia=web

I also like to mention that Debian requires using the source tarball, and prefers having tests to verify the package was installed successfully. Gentoo also has dedicated test phase for this as well.