gh-130197: Test pygettext's --version CLI option

[StanFromIreland]

request: @serhiy-storchaka @tomasr8

• Issue: pygettext: Improve test coverage #130197

[tomasr8]

LGTM. This beyond the scope of this PR but to be honest I'm not even sure we should have a separate version for pygettext (and the --version option). It's distributed together w/ Python so the Python version itself should be enough.

[StanFromIreland]

Friendly ping @serhiy-storchaka

[github-actions]

This PR is stale because it has been open for 30 days with no activity.

[serhiy-storchaka]

LGTM, but the title is confusing.

[StanFromIreland]

Sorry, this is a pretty old PR. Thanks for the review!

[serhiy-storchaka]

And I concur with @tomasr8.

[StanFromIreland]

And I concur with @tomasr8.

I do too, I opened an issue for it a long time ago, but some people objected so it never went ahead.

[StanFromIreland]

I found it: #133319

[bedevere-bot]

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

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

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/2943) and take a look at the build logs.
4. Check if the failure is related to this commit (d63c994) 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/2943

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

Click to see traceback logs

Note: switching to 'd63c9940f0bcc5497c42c6ac2768cdab02300e10'.

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 d63c9940f0bcc gh-130197: Test `pygettext`'s `--version` CLI option (#133022)
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:3446: 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:1157: libpython3.16.a] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:990: profile-gen-stamp] Error 2
make: *** [Makefile:1002: 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 d63c994.

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/2932) and take a look at the build logs.
4. Check if the failure is related to this commit (d63c994) 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/2932

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

Click to see traceback logs

Note: switching to 'd63c9940f0bcc5497c42c6ac2768cdab02300e10'.

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 d63c9940f0bcc gh-130197: Test `pygettext`'s `--version` CLI option (#133022)
Switched to and reset branch 'main'

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