## gpg in pypi is not official

> > 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.

"gpg" is the name of the python gpgme bindings, the official ones.

But the packaging on pypi was not official.
See https://lists.gnupg.org/pipermail/gnupg-devel/2022-November/035167.html


> 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.

As interims holder I have control of the gpg pypi entry, suggestions are welcome how to resolve
and improve the situation. But this is outside of this issue. Send suggestions to gnupg-devel 
(and read the several discussions about this in the past first).

For this case, what should we at roundup do, to roundup's use of GnuPG via gpgme functional and tested.
Is using the official packages for Debian and Ubuntu enough?
And then we need to check if the documentation recommends current packages, either via the distributions or via building it from the upstream releases. And we need to discourage the current pypi entry.