Hi Chris,
> https://lintian.debian.org/tags/python-package-depends-on-package-from-othe
> r-python-variant.html
>
> This won't trigger for packages unless they are called /
> ^python([23]?)-/ however. Indeed, this seems to be required so we
> "know" that a package is a "2" or a "3".
>
> Would this have matched otherwise?
Only module packages are called python{,3}-foo, while applications packages do
not have the binary prefix and we have plenty of python applications packages,
packages that include both applications and private modules or even packages
that include applications and public modules. For all of them, dependencies on
both Python runtimes is most likely still incorrect.
This is probably "Certainty: wild guess" material as I'm sure there are a
handful of legitimate use cases for depending on both Python 2 and Python 3,
but my feeling is that the vast majority of such dependencies would be
mistakes.
(yes, if this were python-translate-toolkit then it would have been caught,
but that package name would also be incorrect for the package)
cheers
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ [email protected]
Debian Developer http://www.debian.org/ [email protected]
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
