[Python-Dev] Python Language Summit at PyCon: Agenda
fijall at gmail.com
Mon Mar 4 20:08:50 CET 2013
On Mon, Mar 4, 2013 at 8:41 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> On Mon, 4 Mar 2013 11:51:04 -0500
> Barry Warsaw <barry at 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.
Please pick a different name though, pytest is already widely used.
More information about the Python-Dev