On Tuesday, January 3, 2023 1:00:28 PM EST Drew Parsons wrote: > 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)
I think this proposal is at least one release cycle too soon. We're close to freeze and in the midst of changing the default python version. At the very least this should wait until Bookworm is out. There should also be a rebuild of the affected packages to see what problems are induced. Maybe, after Bookworm is out, we could get the reproducible builds people to do a special run with a setup.py build followed by a pyproject.toml build so we can see the differences. Scott K
signature.asc
Description: This is a digitally signed message part.
