[issue47133] enhance unittest to show test name and docstring on one line

2022-04-03 Thread Gregory P. Smith
Gregory P. Smith added the comment: A more fundamental issue behind this: unittest's plain text verbose output is not intended to be parsable and consumable by machines. It is 22 years old and was intended for use in 80 column wide terminals as a progress report while watching it run as

[issue47133] enhance unittest to show test name and docstring on one line

2022-03-27 Thread Steven D'Aprano
Steven D'Aprano added the comment: Rather than an option for this, it would be cleaner to deprecate the current output in 3.11, and fix it in 3.12 or 3.13. Otherwise we have to maintain the old (bad?) output and the new output both forever. --

[issue47133] enhance unittest to show test name and docstring on one line

2022-03-27 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: This is already the third (at least) issue asking for such feature. Many people have problems with the current output. I would prefer to have a full qualified name of the test which I can copy by a double click and insert in a command that reruns

[issue47133] enhance unittest to show test name and docstring on one line

2022-03-26 Thread Steven D'Aprano
Steven D'Aprano added the comment: I have no problem with pinging Python-Dev, or any other forum, asking for interested parties. I just don't think we should be intentionally spliting the discussion more than it's going to get split organically. (If this is interesting to people, they will

[issue47133] enhance unittest to show test name and docstring on one line

2022-03-26 Thread Ethan Furman
Ethan Furman added the comment: I proposed a discussion to python-dev to increase the odds that folks with an interest could chime in. Not everyone follows the new-bugs list. I find having the output on two lines counter-intuitive -- I was expecting one line per test, and indeed my

[issue47133] enhance unittest to show test name and docstring on one line

2022-03-26 Thread Steven D'Aprano
Steven D'Aprano added the comment: I don't think this change of behaviour should be accepted without discussion, and I'm not sure why you think Python-Dev is the right place, rather than here. Messing around with unittest and docstrings has already caused issues in the past:

[issue47133] enhance unittest to show test name and docstring on one line

2022-03-26 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Issue14265, issue46126. -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list

[issue47133] enhance unittest to show test name and docstring on one line

2022-03-26 Thread Itay Yeshaya
Itay Yeshaya added the comment: I would like to work on this. -- nosy: +itay.yeshaya ___ Python tracker ___ ___ Python-bugs-list

[issue47133] enhance unittest to show test name and docstring on one line

2022-03-26 Thread Irit Katriel
Change by Irit Katriel : -- keywords: +easy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue47133] enhance unittest to show test name and docstring on one line

2022-03-26 Thread Ethan Furman
Change by Ethan Furman : -- assignee: -> ethan.furman ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue47133] enhance unittest to show test name and docstring on one line

2022-03-26 Thread Ethan Furman
New submission from Ethan Furman : When running unittest with the -v flag, if a test has errors, and has a docstring, the test name is shown on one line, and the docstring is shown on the next line -- and the ERROR word is shown with the docstring. What this means is that: - the test name is