python313Packages.standard-mailcap: init at 3.13.0

[lucc]

This is a replacement for the mailcap module from the python standard lib which was removed for python 3.13. This package will be needed for alot to work under python 3.13.

Repo: https://github.com/youknowone/python-deadlib
PyPI: https://pypi.org/project/standard-mailcap/

(There is no proper homepage)

This fixes #362878.

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/)
• 25.05 Release Notes (or backporting 24.11 and 25.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.

[dotlambda]

Suggested change

	version = "3.13.0";
	disabled = pythonOlder "3.13";
	src = fetchPypi {
	version = "3.13.0";
	pyproject = true;
	disabled = pythonOlder "3.13";
	src = fetchPypi {

[lucc]

pyproject=true is in line 17. Did you miss it or do you want it further at the top?

[dotlambda]

This is the style we usually follow.

[lucc]

I reordered the attributes. Is the order/style (also the pipy vs github stuff) documented somewhere? Or is it just something you learn on the way?

[dotlambda]

fetchFromGitHub is preferred

[lucc]

But the github repo has many subfolders with different "dead batteries" in each subfolder. So I would have to pull one subfolder from the github repo. Is that still preferred?

[dotlambda]

Yes.

[lucc]

I tried this and it looks much more complicated to me.
With fetchPypi I have

src = fetchPypi {
  pname = "standard_mailcap";
  inherit version;
  hash = "sha256-Ge15VdvqzLNei7BbK1RDzlXB+TKoy+elwT1C+dtPSZo=";
};

whereas with fetchFromGitHub I have

src = fetchFromGitHub {
  owner = "youknowone";
  repo = "python-deadlib";
  tag = "v3.13.0";
  hash = "sha256-9mtQi5ufxP6xRonTrFC3oWFpWLbJraAmdQYozP3evgc=";
  sparseCheckout = [ "mailcap" ];
};
preBuild = "cd mailcap";

Just to be absolutely sure: fetchFromGtHub is still preferred in this situation?

[lucc]

@dotlambda I tried to address your comments. Do you mind having another look?