Howdy all, How can I convince ‘dh-python’ to derive package dependencies from the Setuptools ‘install_requires’ declaration?
The Pip requirements tend to be tightly restrictive, because Pip is not a distribution system but rather a deployment system. So those requirements tend not to be good candidates for Debian's versioned dependencies. The Setuptools ‘install_requires’ declaration is a better candidate for this, since it is metadata for the *distribution* (not deployment); this better matches Debian's purposes for package dependencies. See <URL:https://caremad.io/posts/2013/07/setup-vs-requirement/> for a discussion of these complementary and different purposes. How can I convince ‘dh-python’ to derive Debian package dependencies from the Setuptools ‘install_requires’ declaration? For example, <URL:https://mentors.debian.net/debian/pool/main/m/mullvad-client/mullvad-client_60+dfsg.1-1.dsc> declares dependencies that ‘dh_python2’ does not detect; the resulting binary has none of the Python dependent packages declared. -- \ “Capitalism has destroyed our belief in any effective power but | `\ that of self interest backed by force.” —George Bernard Shaw | _o__) | Ben Finney
