Dear Maintainer, I also would support the idea of removing the dh-python dependency from python3.
I'm like the original bug reporter unhappy with the new transitive dependency from dh-python to dpkg-dev which pulls unwanted development packages in. But reading the other bug reports it seems that a dep from dh-python to dpkg-dev makes actually sense. So removing the dep from python3 to dh-python is the right thing to do, imho. It is the clean solution, which also forces bugfixes in other packages. Like the others said python3 is an end-user runtime, dh-python a development tool. It should be possible to run a Debian system without development tools (there are already to many of them force-installed!). I run all my dev stuff in containers, and don't like that stuff also on my desktop installed in parallel. It makes no sense and only widens the attack surface for security exploits. So please consider improving the current situation by removing the dep from python3 to dh-python. It would even enhance other packages by making fixes of their dependencies mandatory. Thank you for all that great work on Debian! With kind regards Mateusz
