python3Packages.sipsimple: fix build with gcc15; refactor and modernize

[eljamm]

Changes

• Fix build with gcc15 (tracking Some packages may fail to compile with GCC 15 #475479)
• Refactor and modernize
  • Follow upstream and rename from sipsimple to python3-sipsimple
  • Use finalAttrs fixpoint pattern (buildPython*: support fixed-point arguments #271387)

Things done

• 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.

[Prince213]

Mostly LGTM.

[eljamm]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review
Commit: 1b6bf4b9aacc0bcd3f6c8d4533b28b13d7afe552

---

x86_64-linux

✅ 8 packages built:

• blink-qt
• blink-qt.dist
• python313Packages.python3-sipsimple
• python313Packages.python3-sipsimple.dist
• python314Packages.python3-sipsimple
• python314Packages.python3-sipsimple.dist
• sylkserver
• sylkserver.dist

[eljamm]

Is there anything else that should be done? the fix is more important to me than the refactors, so I can split the latter into a followup if it needs more work/discussion.

[nixpkgs-ci]

Successfully created backport PR for release-25.11:

• [Backport release-25.11] python3Packages.sipsimple: fix build with gcc15; refactor and modernize #478090

[dotlambda]

I'd follow the majority on Repology and use

Suggested change

	python3-sipsimple = callPackage ../development/python-modules/python3-sipsimple { };
	sipsimple = callPackage ../development/python-modules/sipsimple { };

[eljamm]

It is called python:sipsimple in repology, but not in the distros' repos? for example in the AUR it's python-sipsimple.

[dotlambda]

That's Arch's standard prefix for Python packages.

[eljamm]

Ah, thanks for the info, that's good to know. Would you suggest renaming it again or would it be fine to keep it as python3-sipsimple since it's already like this in repology? If it's the former, perhaps we could do it for all similar packages?

[dotlambda]

Actually, python3-sipsimple is correct in this case:

• https://github.com/AGProjects/python3-sipsimple/blob/5.3.3.2-mac/sipsimple/__info__.py#L4
• https://github.com/AGProjects/python3-sipsimple/blob/5.3.3.2-mac/setup.py#L29

It's what ends up in the METADATA file in the output.