Future of GpgME python bindings on PyPi

[Paul Schwabauer]

The current PyPi entry for the GpgMe bindings 
(https://pypi.org/project/gpg/) is unmaintained. Unfortunately, some 
projects, like Roundup for GPG support, still rely on this entry. The 
outdated version of the bindings contains an invalid code sequence that 
causes compatibility issues with newer Python versions (for more 
details, see the issue: https://issues.roundup-tracker.org/issue2551368).

There are two potential courses of action:

 1.

    *Declare the entry as unmaintained*: Notify all users that this
    package should no longer be used and recommend alternative, actively
    maintained bindings.

 2.

    *Assign a maintainer to the PyPi entry*: Upload a new version and
    fix the build issues to ensure proper functionality.

Currently, the existing Python bindings cannot correctly build a source 
distribution due to missing files in the package. I had to use 
workarounds to build the distribution. For reference, here are the steps 
I followed to successfully build the package: 
https://issues.roundup-tracker.org/msg8362.

For testing purposes, I uploaded a version of the bindings to the PyPi 
testing index: https://test.pypi.org/project/gpg/.

At present, Bernhard Reiter has access to the GPG entry. I would like to 
extend access to someone with write access to the |gpgmepy| repository 
who is interested in maintaining and uploading new versions of the 
bindings. Ideally, I hope this entry continues to be updated, as doing 
so could help identify issues that might affect users who do not 
directly use the bindings via PyPi.