[issue30318] test_distutils is too verbose on Windows

Change by STINNER Victor : -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-

[issue30318] test_distutils is too verbose on Windows

STINNER Victor added the comment: > The problem here I think is that distutils itself should only dump > stdout/stderr on failure, ... Hum, I would like to see warnings even if the compilation succeed. So I would prefer to only modify test_distutils. -- __

[issue30318] test_distutils is too verbose on Windows

Steve Dower added the comment: The problem here I think is that distutils itself should only dump stdout/stderr on failure, but because of how it spawns processes it never actually captures the output from external tools. We really need to update distutils's spawn() function to use subprocess.

[issue30318] test_distutils is too verbose on Windows

Changes by Jeremy Kloth : -- nosy: +jkloth ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue30318] test_distutils is too verbose on Windows

New submission from STINNER Victor: test_distutils should only dump stdout/stderr on compilation failure, but hide them on success (by default). Example of output: http://buildbot.python.org/all/builders/x86%20Windows7%203.x/builds/588/steps/test/logs/stdio 0:58:52 [277/405/1] test_distutils