[issue22431] Change format of test runner output

2020-07-24 Thread Zackery Spytz
Change by Zackery Spytz : -- keywords: +patch nosy: +ZackerySpytz nosy_count: 8.0 -> 9.0 pull_requests: +20751 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21609 ___ Python tracker

[issue22431] Change format of test runner output

2016-10-19 Thread Jon Dufresne
Changes by Jon Dufresne : -- nosy: +jdufresne ___ Python tracker ___ ___

[issue22431] Change format of test runner output

2016-09-20 Thread Robert Collins
Robert Collins added the comment: +1 to changing the UI for 3.7 - just noting that if you're machine processing the output, the TUI isn't an appropriate channel. -- ___ Python tracker

[issue22431] Change format of test runner output

2016-09-20 Thread R. David Murray
R. David Murray added the comment: My understanding of the comments is that the change to the default is OK (in a feature release, at least). -- versions: +Python 3.7 -Python 3.5 ___ Python tracker

[issue22431] Change format of test runner output

2016-09-20 Thread Tim Graham
Tim Graham added the comment: Here's the patch if we make the change in Django instead: https://github.com/cjerdonek/django/commit/9c8d162f3f616e9d9768659a06fcf27bb389214b -- ___ Python tracker

[issue22431] Change format of test runner output

2016-09-20 Thread Tim Graham
Tim Graham added the comment: Is there opposition to changing the default output as outlined in the first comment? If so, then I think this ticket should be closed or retitled to reflect the intent. -- nosy: +Tim.Graham ___ Python tracker

[issue22431] Change format of test runner output

2014-11-13 Thread Robert Collins
Robert Collins added the comment: Yes, making customising the output easier is a good thing. One way is to use e.g. subunit.run (which can work with all unittest versions since 2.6) and write a custom filter. Or a custom TestResult and TextTestRunner can work too :) --

[issue22431] Change format of test runner output

2014-11-10 Thread Michael Foord
Michael Foord added the comment: I agree with Robert that the text output of the default runner should not be considered a part of the api that we make backwards compatible guarantees about. People who want to customise that should be customising the text runner/result. (Unfortunately it

[issue22431] Change format of test runner output

2014-11-07 Thread Robert Collins
Robert Collins added the comment: I don't consider the console output of unittest to be a stable interface. Michael - do you? Things that want to process unittest should be using the API. -- nosy: +rbcollins ___ Python tracker

[issue22431] Change format of test runner output

2014-11-07 Thread Antoine Pitrou
Antoine Pitrou added the comment: I agree with Robert. However, since software authors' wishes can clearly be diverse here, perhaps there should be a simple way for them to customize the output? -- nosy: +pitrou ___ Python tracker

[issue22431] Change format of test runner output

2014-09-17 Thread Philipp Metzler
New submission from Philipp Metzler: Can I change the test runner output format to main.tests.tests.TimeSlotTestCase.test_creation ... ERROR instead of test_creation (main.tests.tests.TimeSlotTestCase) ... ERROR so that I can easily just copypaste that line and run the test again without having

[issue22431] Change format of test runner output

2014-09-17 Thread R. David Murray
R. David Murray added the comment: I remember this feature being requested before (I vote +1 myself :), and I believe I recall a conversation involving Michael Foord where he approved it in principle, but I can't find an open issue for it. As a new feature it can only go into 3.5, and would

[issue22431] Change format of test runner output

2014-09-17 Thread Martin Panter
Changes by Martin Panter vadmium...@gmail.com: -- nosy: +vadmium ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22431 ___ ___ Python-bugs-list