[Python-Dev] Python Language Summit at PyCon: Agenda

Michael Foord fuzzyman at voidspace.org.uk
Tue Mar 5 01:21:58 CET 2013

On 4 Mar 2013, at 19:26, Berker Peksağ <berker.peksag at gmail.com> wrote:

> On Mon, Mar 4, 2013 at 9:14 PM, Barry Warsaw <barry at python.org> 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

Indeed, and unittest2 (the backport) which has to work with Python 2.6 (where "python -m package_name" doesn't work) has "unit2" as a shortcut. So it has an advantage over the standard library version here.

I'd like to see pyunit as a short-cut for "python -m unittest discover", with a "pyunit-3.x" variant too. 

Barry objects that Linux distributions won't want to support all of these, which is frankly their problem.


> --Berker
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk


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 

More information about the Python-Dev mailing list