Issue 42790: test.regrtest outputs to stdout instead of stderr

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/86956

classification

Title:	test.regrtest outputs to stdout instead of stderr
Type:	behavior	Stage:
Components:	Tests	Versions:

process

Status:	open	Resolution:
Dependencies:		Superseder:
Assigned To:		Nosy List:	serhiy.storchaka, vstinner
Priority:	normal	Keywords:

Created on 2020-12-30 19:26 by serhiy.storchaka, last changed 2022-04-11 14:59 by admin.

Messages (1)
msg384084 - (view)	Author: Serhiy Storchaka (serhiy.storchaka) *	Date: 2020-12-30 19:26
unittest outputs progress and summary to stderr, but test.regrtest outputs it to stdout. Except that it outputs progress to stderr if option -W is used. It caused some problems with test_curses, because curses uses stdout, and when re-attach it to other terminal or file we can lose the regrtest output. It makes the code more complicated.

msg384084 - (view)

Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer)

Date: 2020-12-30 19:26

unittest outputs progress and summary to stderr, but test.regrtest outputs it to stdout. Except that it outputs progress to stderr if option -W is used.

It caused some problems with test_curses, because curses uses stdout, and when re-attach it to other terminal or file we can lose the regrtest output. It makes the code more complicated.

History
Date	User	Action	Args
2022-04-11 14:59:39	admin	set	github: 86956
2020-12-30 19:26:59	serhiy.storchaka	create