The reason for the failing installation is this line in setup.py:
```
line_break = re.compile(';|\\$|\\x0c|^\s*#|{')
```
`\s` is not a valid escape character and, therefore, not valid Python code. Before Python 3.12, this resulted in a deprecation warning; with Python 3.12, this is no longer allowed.

A workaround can be to build the bindings yourself using the upstream version. Here is an example of how to do this with the current CI: https://github.com/koplas/roundup/commit/6120422aa2686a23997592a58d41139fe223ec2f.

Here is the running workflow: https://github.com/koplas/roundup/actions/runs/13729858872/job/38404537982.

The upstream support for creating packages that can be built and uploaded to PyPi is currently broken (I guess this has not been tested, as there are no up-to-date gpgme bindings on PyPi).

> Unfortunately the pip package was never official.
It is official, citing the README of the upstream repository:
> The python bindings were renamed from PyME to “gpg” in 2016.

The official setup.py also uses the name gpg; if this is not official, the upstream developers should strive to take over the package name or at least replace it with a dummy package.

If only the CI needs to be fixed, it should be enough to install the already mentioned python3-gpg package. The Python bindings were recently moved to a separate repository: https://github.com/gpg/gpgme/commit/932caf37d36eca2caec59bf48bc505364a5765bb, and it may be better to contact the developers to restore the maintenance of the PyPi package.