On Mon, Mar 4, 2013 at 8:41 PM, Antoine Pitrou <solip...@pitrou.net> wrote: > On Mon, 4 Mar 2013 11:51:04 -0500 > Barry Warsaw <ba...@python.org> wrote: >> On Mar 04, 2013, at 11:34 AM, Brett Cannon wrote: >> >> >> And One True Way of invoking and/or discovering how to invoke, a package's >> >> test suite. >> > >> >How does unittest's test discovery not solve that? >> >> I should have added "from the command line". E.g. is it: >> >> $ 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. > > Regards > > Antoine.
Please pick a different name though, pytest is already widely used. _______________________________________________ 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/archive%40mail-archive.com
