[Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda) (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Tue Mar 5 23:44:34 CET 2013
- Previous message: [Python-Dev] built-in Python test runner
- Next message: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 6 Mar 2013 05:51, "Barry Warsaw" <barry at python.org> wrote:
On Mar 05, 2013, at 02:11 AM, Donald Stufft wrote: >Doesn't setuptools/distribute already have a setup.py test command? That >seems like the easiest way forward? Yes, and in theory it can make
python setup.py test
work well. But there are lots of little details (such as API differences for ensuring that doctests run, "additional tests" discovery, etc.) that make this often not work so well in practice. Some of that is social and some of it is technical. I still claim that including test suite information in a package's metadata would be a win, but maybe that's just too much to hope for right now.
I think it's the right answer, too, but PEP 426 is already huge, so metadata 2.1 is likely the earliest we will try to tackle the problem.
Cheers, Nick.
-Barry
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/ncoghlan%40gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20130306/58cd1621/attachment.html>
- Previous message: [Python-Dev] built-in Python test runner
- Next message: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]