Package: dh-python Version: 5.20221230 Severity: normal Our pyproject (PEP517) build system now seems to be operating reliably. Using the old default system with setup.py, we now get reminded that it is deprecated. In some cases the old default setup method is even "harmful" in the sense of running configuration twice, once for the build rule and again for the install rule (arguably this could be seen as a bug in the setup.py).
We had to introduce pyproject (pybuild-plugin-pyproject) when python modules started appearing with a pyproject.toml and no setup.py file. But now we're in the reverse situation: a pyproject build can proceed (using rules in setup.py) even if there is no pyproject.toml file. So pyproject builds now seem to be the superior option, even when there is an old setup.py file with no pyproject.toml. For that reason I propose switching pybuild to start using pyproject as the default system rather than distutils. (I expect this would need dh-python Depends: pybuild-plugin-pyproject) -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dh-python depends on: ii python3 3.10.6-3+b1 ii python3-distutils 3.10.8-1 dh-python recommends no packages. Versions of packages dh-python suggests: ii dpkg-dev 1.21.15 ii flit 3.8.0-2 ii libdpkg-perl 1.21.15 ii python3-build 0.9.0-1 ii python3-installer 0.6.0+dfsg1-1 ii python3-tomli 2.0.1-2 -- no debconf information
