[Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda) (original) (raw)
Robert Collins robertc at robertcollins.net
Mon Mar 4 23:01:38 CET 2013
- Previous message: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)
- Next message: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5 March 2013 10:26, Eli Bendersky <eliben at gmail.com> wrote:
[Splitting into a separate thread]
Do we really need to overthink something that requires a trivial alias to set up for one's own convenience?
The big thing is automated tools, not developers.
When distributors want to redistribute packages they want to be sure they work. Running the tests is a pretty good signal for that, but having every package slightly different adds to the work they need to do. Being able to do 'setup.py test' consistently, everywhere - that would be great.
-Rob
-- Robert Collins <rbtcollins at hp.com> Distinguished Technologist HP Cloud Services
- Previous message: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)
- Next message: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]