test_curses.test_use_default_colors fails on some platforms

[picnixz]

Bug report

Bug description:

I'm pretty sure it's either my own configuration (openSUSE 15.5 + custom konsole) or my curses version (6.1) but here it is:

$ ./python -m test test_curses -ucurses
Using random seed: 3209469927
0:00:00 load avg: 2.41 Run 1 test sequentially in a single process
0:00:00 load avg: 2.41 [1/1] test_curses
test test_curses failed -- Traceback (most recent call last):
  File "~/lib/python/cpython/Lib/test/test_curses.py", line 49, in wrapped
    test(self, *args, **kwargs)
    ~~~~^^^^^^^^^^^^^^^^^^^^^^^
  File "~/lib/python/cpython/Lib/test/test_curses.py", line 999, in test_use_default_colors
    self.assertIn(old, [(curses.COLOR_WHITE, curses.COLOR_BLACK), (-1, -1), (0, 0)])
    ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: (15, 0) not found in [(7, 0), (-1, -1), (0, 0)]

0:00:00 load avg: 2.41 [1/1/1] test_curses failed (1 failure)

When I want to test curses, I usually skip over this one.

The cause

The current terminal fg/bg colors given by pair_content(0), which is backed by extended_pair_content(3), depends on the terminal emulator and its supported colors. Thus, its output cannot not be reliably checked.

CPython versions tested on:

CPython main branch

Operating systems tested on:

No response

Linked PRs

• gh-91221: remove unreliable checks on curses.pair_content(0) #132986

[serhiy-storchaka]

This is a duplicate of #91221.

[picnixz]

Oh! my bad. I'll close this one then.