gh-139445: Skip pyrepl tests if the terminal is not supported

[serhiy-storchaka]

TestMain was only skipped if TERM was unset or dumb, but pyrepl needs the terminal to have the bel, clear, cup and el capabilities. Without them it falls back to the basic REPL, and six tests which type bare exit wait for the timeout.

Checking the capabilities subsumes the unset/dumb case.

• Issue: some tets will fail like test_pyrepl when can't use pyrepl #139445

[edvilme]

Is the use of _colorize.get_colors relevant here?

cpython/Lib/_colorize.py

Line 548 in 3479e45

def get_colors(

[serhiy-storchaka]

Yes, can_colorize() has the same TERM=dumb-only check. But there it is probably harmless: ANSI colors work even on terminals like TERM=su that lack the cursor-movement capabilities (cup etc.) pyrepl needs.

[miss-islington-app]

Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14, 3.15.
🐍🍒⛏🤖

[miss-islington-app]

Sorry, @serhiy-storchaka, I could not cleanly backport this to 3.14 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker 7745710bec7f6de899e97d6f87528035e8977d85 3.14

[bedevere-app]

GH-154530 is a backport of this pull request to the 3.14 branch.

[bedevere-app]

GH-154529 is a backport of this pull request to the 3.15 branch.

[bedevere-bot]

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot s390x Fedora Stable LTO + PGO 3.x (tier-3) has failed when building commit 7745710.

What do you need to do:

1. Don't panic.
2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1627/builds/3093) and take a look at the build logs.
4. Check if the failure is related to this commit (7745710) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1627/builds/3093

Summary of the results of the build (if available):

Click to see traceback logs

Note: switching to '7745710bec7f6de899e97d6f87528035e8977d85'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 7745710bec7f6 gh-139445: Skip pyrepl tests if the terminal is not supported (GH-154497)
Switched to and reset branch 'main'

find: ‘build’: No such file or directory
find: ‘build’: No such file or directory
find: ‘build’: No such file or directory
find: ‘build’: No such file or directory
make[2]: [Makefile:3474: clean-retain-profile] Error 1 (ignored)
./Modules/socketmodule.c: In function ‘getsockaddrarg’:
./Modules/socketmodule.c:2646:9: warning: ‘strncpy’ specified bound 64 equals destination size [-Wstringop-truncation]
 2646 |         strncpy((char *)sa->salg_name, name, sizeof(sa->salg_name));
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ar: unable to copy file 'libpython3.16.a'; reason: No space left on device
make[2]: *** [Makefile:1163: libpython3.16.a] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:996: profile-gen-stamp] Error 2
make: *** [Makefile:1008: profile-run-stamp] Error 2

[bedevere-bot]

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot s390x Fedora Stable LTO 3.x (tier-3) has failed when building commit 7745710.

What do you need to do:

1. Don't panic.
2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1654/builds/3070) and take a look at the build logs.
4. Check if the failure is related to this commit (7745710) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1654/builds/3070

Summary of the results of the build (if available):

Click to see traceback logs

Note: switching to '7745710bec7f6de899e97d6f87528035e8977d85'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 7745710bec7f6 gh-139445: Skip pyrepl tests if the terminal is not supported (GH-154497)
Switched to and reset branch 'main'

ar: unable to copy file 'libpython3.16.a'; reason: No space left on device
make: *** [Makefile:1163: libpython3.16.a] Error 1