On 15-Dec-2016, Matthias Klose wrote: > In the past we needed that [split into ‘python-pkg-resources’ and > ‘python-setuptools’ binary packages] to be able to build packages > without setuptools but using pkg_resources.
Yes, that's exactly my purpose for depending on
‘python-pkg-resources’. What are you saying has changed? As far as I
can tell there is still the need to have ‘pkg_resources’ available
separately.
The ‘dh-python’ suite is currently detecting dependencies from the
Distutils information; the binary package has only “${python:Depends}”
which is then populated automatically. Is this perhaps a bug in that
detection? What should I describe to the ‘dh-python’ maintainer?
--
\ “If you're a horse, and someone gets on you, and falls off, and |
`\ then gets right back on you, I think you should buck him off |
_o__) right away.” —Jack Handey |
Ben Finney <bign...@debian.org>
signature.asc
Description: PGP signature
