[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#836710: dput: Handle ‘setuptools’ specially to work around circular dependency



Control: reassign -1 dput
Control: found -1 dput/0.10.3
Control: found -1 dput/0.11.0
Control: tags -1 + help

On 17-Dec-2016, Ben Finney wrote:
> 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.

I haven't had an explanation of what is different now, so I'm casting
to the Debian Python community for help.

Please keep bug#836710 in the correspondence so that I can track the
discussion.


Other unresolved questions:

> 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?

On 19-Dec-2016, Ben Finney wrote:
> 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.

I'd appreciate help with understanding what needs to be done, and how
the tools should be configured to do it automatically.

-- 
 \         “Pinky, are you pondering what I'm pondering?” “I think so, |
  `\   Brain, but why does a forklift have to be so big if all it does |
_o__)                           is lift forks?” —_Pinky and The Brain_ |
Ben Finney <bignose@debian.org>

Attachment: signature.asc
Description: PGP signature


Reply to: