Request: New release including fix from PR #86
Hi, thanks for maintaining GenSON!
PR #86 ("fix: include genson.schema submodule in package build") was merged
into master on 2025-09-06. It fixes a packaging bug in setup.cfg where
was changed to
packages = find:
[options.packages.find]
include = genson*
This bug causes the genson.schema (and genson.schema.strategies) subpackages
to be missing after installation, making every import fail immediately:
ModuleNotFoundError: No module named 'genson.schema'
The issue was originally reported in #80 and is also documented in the Debian
packaging mailing list (ITP: python-genson, January 2025).
Impact
As long as v1.3.0 remains the latest release, every downstream packager
(Debian, NixOS, Arch, Homebrew, etc.) must carry a workaround patch to fix
the installation. Specifically, a new release would:
- Allow the NixOS/nixpkgs package to be submitted without a postPatch workaround
- Unblock Debian (see ITP bug report)
- Prevent confusion for users who install via
pip install genson==1.3.0
and get a broken package
Ask
Could you please tag a new release (e.g. v1.3.1) from the current master
HEAD (a143f68d) so the fix becomes part of an official release?
Thanks a lot!
Request: New release including fix from PR #86
Hi, thanks for maintaining GenSON!
PR #86 ("fix: include genson.schema submodule in package build") was merged
into
masteron 2025-09-06. It fixes a packaging bug insetup.cfgwherewas changed to
This bug causes the
genson.schema(andgenson.schema.strategies) subpackagesto be missing after installation, making every import fail immediately:
The issue was originally reported in #80 and is also documented in the Debian
packaging mailing list (ITP: python-genson, January 2025).
Impact
As long as
v1.3.0remains the latest release, every downstream packager(Debian, NixOS, Arch, Homebrew, etc.) must carry a workaround patch to fix
the installation. Specifically, a new release would:
pip install genson==1.3.0and get a broken package
Ask
Could you please tag a new release (e.g.
v1.3.1) from the currentmasterHEAD (
a143f68d) so the fix becomes part of an official release?Thanks a lot!