On Fri, Aug 05, 2016 at 08:37:24PM +0200, David Craven wrote:
> * gnu/packages/python.scm (python-pymongo): New package.
> (python2-pymongo): New package.
s/package/variable
> + (inputs
> + `(("python-certifi" ,python-certifi)
> + ("python-setuptools" ,python-setuptools)))
I notice several of these patches include setuptools as an input to the
Python 3 variant of the package.
While some Python 3 packages require setuptools, most don't, whereas
most Python 2 packages do require setuptools.
We have a "python2-variant" system that we use when the Python 2 version
of some package requires a different set of inputs from the Python 3
version that it is based on. There is a good example in python-lockfile
/ python2-lockfile.
It adds a few lines of code but if we use it consistently, it will
drastically reduce the number of packages that depend on
python-setuptools.
Can you check this patch series to see if the Python 3 variants require
setuptools?
