Barry Warsaw wrote: > The standard for running a Python package's test suite is > > $ python setup.py test
How standard? Ie, I picked a random python package,aand: joey@gnu:~/tmp/python-mpd-0.3.0>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' So I picked another one: joey@gnu:~/tmp/jabber.py-0.5.0>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' So I tried one more: joey@gnu:~/tmp/python-memcache-1.47>python setup.py test running test Well, finally. (Not much of a test suite tho.) Perhaps you meant to say that's the standard for a python package that uses setuptools, rather than distutils? Or something more complicated. > dh_auto_test should support this for Python packages. It might also > make sense to use this in preference to running 'make check' even if > there is a Makefile present. FWIW, dh_auto_test never runs make test/check on python packages. -- see shy jo
signature.asc
Description: Digital signature
