Package: dh-python Followup-For: Bug #1027864 Mind you, the build module for PEP517 builds seems not to give good control of build and build-temp dirs. For example, the temp dir for building python extensions gets placed in build rather than .pybuild, which is not in the spirit of the pybuild tool. python3 -m build does not seem to have options for controlling the location of the build dirs. It might be possible to pass it to the underlying setup.py using the -C flag, but I couldn't get that to work easily from debian/rules It would require running pybuild manually with a separate -p option for each python version. Perhaps this is a feature which could be addressed in pybuild.
It matters in particular for python modules which are rebuilt with different configurations, for different debian python packages from the same source. For instance petsc4py provides separate real and complex number builds of its python module. So perhaps it's premature to use pyproject by default until there's better control of the build dirs used for pybuild. On the other hand, perhaps it's nevertheless still worth setting pyproject as the default system, to accommodate the simpler packages. The petsc4py build can't really be called "simple", so doesn't necessarily need to influence discussion of the default system. It needs to retain a distutils build for now, which can be managed from its debian/rules.
