> Those will correspond to build dependencies in a typical simple case, as > the upstream tests need all those optional deps, assuming you mean the > tests dependencies (and not the runtime dependencies which should already > be in Depends).
Yes the runtime dependencies should be listed in the python3-<module> Depends: > >> Maybe we should install only the python binaries and the dependencies marked >> <!nocheck>. > > In a typical simple case all B-Ds except sphinx stuff will be <!nocheck> > as you don't need anything beyond the build system to "build" a pure > Python module. > So this is exactly what you wanted to avoid. Yes, I want to be sure that all the runtime dependencies are rightfully declared in the Depends of the python module package. sometimes the upstream forgot about dependencies, or mark them as optional, but they are not when running the tests... Is it possible to achieve this automatically ? lintian ? dh-python ? python3-stdeb ? Fred. PS: In haskell we have a cabal-debian package which compute automatically the list of the Dependencies, from the cabal file, then it update the control file to reflect the new status of the package.
