dye setup.py uses distutils.core.setup instead of setuptools.setup
Created by: qris
We used dye's setup.py
as an example for cmsbootstrap
. I got stuck trying to make it run tests, with the following error:
chris@lin-vnc2:~/cmsbootstrap$ /tmp/ve/bin/python ./setup.py test
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'test'
The problem turned out to be that we (and DYE) started setup.py
with this line:
from distutils.core import setup
instead of:
from setuptools import setup
as described on Stack Overflow.
This might not be affecting DYE right now, if there are no tests, but is there a reason for using setup
from distutils
instead of setuptools
that we should be aware of? Or does it make sense to change DYE to use setuptools
instead?