On 05-Sep-2016, Ben Burton wrote: > I'm not sure whether the python-setuptools dependency belongs in > dput or in pkg_resources (which currently declares python-setuptools > as a mere Suggests:),
That fact is now a separate report, in bug#840673. It is considered a bug in upstream's handling of ‘pkg_resources’. > but it appears that dput cannot run without it. This bug report tracks that problem. On 15-Dec-2016, Matthias Klose wrote: > On 15.12.2016 21:01, Ben Finney wrote: > > The ‘setuptools’ library *is* needed to build the package. Are you > > saying that it does not belong in the ‘install_requires’ list? > > my understanding is that the exception is raised when people try to > run dput without having python-setuptools installed. Okay. Is there a better way to represent the build dependency on ‘setuptools’, without falsely declaring that it's needed for run-time use? > so yes, for the debian context, you should remove it from the > ‘install_requires’ list and make sure that python-pkg-resources ends > up in the package's Depends. How do you suggest that should be achieved, without special handling for ‘pkg_resources’ only? I would much prefer that dependencies are automatically discovered from the build system's declarations. -- \ “'Tis strange, — but true; for truth is always strange; / | `\ Stranger than fiction.” —“Lord” George Gordon Noel Byron, _Don | _o__) Juan_ | Ben Finney <bign...@debian.org>
signature.asc
Description: PGP signature
