On 4 Mar 2013, at 20:02, Daniel Holth email@example.com wrote:
On Mon, Mar 4, 2013 at 2:26 PM, Berker Peksağ firstname.lastname@example.org wrote:
On Mon, Mar 4, 2013 at 9:14 PM, Barry Warsaw email@example.com wrote:
On Mar 04, 2013, at 07:41 PM, Antoine Pitrou wrote:
$ python -m unittest discover $ python setup.py test $ python setup.py nosetests $ python -m nose test $ nosetests-X.Y
Besides having a multitude of choices, there's almost no way to automatically discover (e.g. by metadata inspection or some such) how to invoke the tests. You're often lucky if there's a README.test and it's still accurate.
I hope we can have a "pytest" utility that does the right thing in 3.4 :-) Typing "python -m unittest discover" is too cumbersome.
Where is this work being done (e.g. is there a PEP)?
There is an open issue on the tracker: http://bugs.python.org/issue14266
setup.py's setup(test_suite="x")... not sure if this is a distutils or setuptools feature. PEP 426 has an extension mechanism that could do the job.
This is a setuptools extension. There was some discussion for packaging/distutils2 of having test support but I have no idea if that has been picked up for the new bunch of packaging related work.
Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.u...
May you do good and not evil May you find forgiveness for yourself and forgive others May you share freely, never taking more than you give. -- the sqlite blessing http://www.sqlite.org/different.html