[Python-Dev] Python Language Summit at PyCon: Agenda (original) (raw)

David Cournapeau cournape at gmail.com
Mon Mar 4 17:44:16 CET 2013

On Mon, Mar 4, 2013 at 4:34 PM, Brett Cannon <brett at python.org> wrote:

On Mon, Mar 4, 2013 at 11:29 AM, Barry Warsaw <barry at python.org> wrote: On Mar 04, 2013, at 07:26 PM, Robert Collins wrote: >It is of course possible for subunit and related tools to run their >own implementation, but it seems ideal to me to have a common API >which regular unittest, nose, py.test and others can all agree on and >use : better reuse for pretty printers, GUI displays and the like >depend on some common API. 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?

It is not always obvious how to test a package when one is not familiar with it. Are the tests in pkgname/tests or tests or ... ?

In the scientific community, we have used the convention of making the test suite available at runtime with pkgname.tests().

David

More information about the Python-Dev mailing list