[Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda) (original) (raw)

Eli Bendersky eliben at gmail.com
Tue Mar 5 01:35:41 CET 2013

On Mon, Mar 4, 2013 at 4:09 PM, Robert Collins <robertc at robertcollins.net>wrote:

On 5 March 2013 12:49, Eli Bendersky <eliben at gmail.com> wrote: > > On Mon, Mar 4, 2013 at 2:14 PM, Barry Warsaw <barry at python.org> wrote: >> >> On Mar 05, 2013, at 11:01 AM, Robert Collins wrote: >> >> >The big thing is automated tools, not developers. >> >> Exactly. > > I don't understand. Is "python -m unittest discover" too much typing for > automatic tools? If anything, it's much more portable across Python versions > since any new coommand/script won't be added before 3.4, while the longer > version works in 2.7 and 3.2+

It isn't about length. It is about knowing that that is what to type (and btw that exact command cannot run twisted's tests, among many other projects tests). Perhaps we are talking about different things. A top level script to run tests is interesting, but orthogonal to the thing Barry was asking for.

Perhaps :-) I'm specifically referring to a new top-level script that will run all unittests in discovery mode from the current directory, as a shortcut to "python -m unittest discover". ISTM this is at leas in part what was discussed, and my email was in this context.

Eli -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20130304/65883813/attachment.html>

More information about the Python-Dev mailing list