Package: dh-python Version: 2.20160818 Severity: wishlist Hi,
As per the dh_python2(1) manpage, version requirements are ignored by default. Explanation is in bug #834809. However, when the maintainer specifies minimum versions in Build-Depends, these versions should be taken as binding for the project. That is, if I Build-Depends: python-foo (>= 1.2), then the generated dependency on python-foo should also be (at least) >= 1.2. There is precedent with the availability of .so-to-dev-package mapping provided by the deb-symbols(5) file, where the Build-Depends version is applied as a constraint to the generated dependency, even if the symbols only require an older version. This would avoid having to specify versioned dependencies for every non-PEP386 module multiple times. -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dh-python depends on: pn python3:any <none> dh-python recommends no packages. Versions of packages dh-python suggests: ii libdpkg-perl 1.18.10 -- no debconf information
