Bug report

Bug description:

If you runFORCE_COLOR=1 make test, many tests fail. The failing tests are mostly due to tests which assert the contents of a traceback not expecting traceback to be colorised, but if you passFORCE_COLOR=1, it seems like Python obediently colorises all traceback.

The full list of failing tests on my machine is:

20 tests failed:    test.test_inspect.test_inspect test_capi test_cmd_line    test_cmd_line_script test_compileall test_doctest test_eof    test_exceptions test_idle test_interpreters test_regrtest    test_repl test_runpy test_signal test_sys test_threading    test_traceback test_tracemalloc test_unicodedata test_warnings

test_signal andtest_ssl seem to fail on my machine withoutFORCE_COLOR being set, however, so those are probably unrelated.

Attached is the full output from running./python.exe -E -m test_traceback -v (which is too long to paste into this issue body directly).

test_traceback.txt

CPython versions tested on:

CPython main branch

Operating systems tested on:

macOS