Package: dh-python Version: 4.20200925 Severity: normal pyproject.toml (PEP 518) is the New Thing for python module builds. Many projects have switched to it, deleting setup.py and introducing a pyproject.toml file.
pybuild currently does not support pyproject.toml. When upstream switches to PEP 518, the package build suddenly starts to fail e.g. dmsh fakeroot debian/rules clean dh clean --with python3 --buildsystem=pybuild dh_auto_clean -O--buildsystem=pybuild I: pybuild base:217: python3.9 setup.py clean python3.9: can't open file '/projects/build/python-dmsh/setup.py': [Errno 2] No such file or directory E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=2: python3.9 setup.py clean dh_auto_clean: error: pybuild --clean -i python{version} -p "3.9 3.8" returned exit code 13 make: *** [debian/rules:5: clean] Error 13 dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2 There is partial support for pyproject.toml builds using flit (PEP 517 builds). But as the pybuild man page says, "These can be identified by the presence of a build-backend = "flit_core.buildapi" element in pyproject.toml." flit doesn't support pyproject.toml builds in general. Filing this bug to request more general support for pyproject.toml builds. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dh-python depends on: ii python3 3.8.6-1 ii python3-distutils 3.8.6-1 dh-python recommends no packages. Versions of packages dh-python suggests: ii dpkg-dev 1.20.5 ii libdpkg-perl 1.20.5 -- no debconf information