gpgmepy Maintainer (needed) Re: python-gpg 2.0.0 from gpgmepy.git on pypi

Bernhard Reiter bernhard at intevation.de
Fri May 8 12:28:52 CEST 2026


Am Freitag 08 Mai 2026 11:43:44 schrieb Werner Koch via Gnupg-devel:
> On Thu,  7 May 2026 16:46, Bernhard Reiter said:
> > Werner,
> > I've put in a branch `pypi-pub-process` with a Dockerfile to document
> > and make the process more repeatable. Is it okay to merge this with the
> > main branch?
>
> I have no idea about the Python support;

This was a general question if you had reservations against using Dockerfile
as a specific way to document the needed technical steps for publication.
I understand that this is not the case. - thanks.

[gpgmepy Maintainership]

> I thought you take care about it.

As explained in March 2025 on this list:
I am doing some interims maintainership with Intevation.

So gpgmepy is still looking for more contributors and a new maintainer!

For the meantime, the goal was to get the current existing bindings at least 
published on pypi for visibility and to support other python devs at little 
bit. Paul Schwabauer was doing most of the work, but he left Intevation last 
fall. So it took me a while to get it done (until yesterday).

For the GnuPG ecosystem I believe that supporting bindings and other devs 
using them, e.g. from the python community, is really helpful. 

Best Regards,
Bernhard
-- 
https://intevation.de/~bernhard   +49 541 33 508 3-3
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260508/e2856212/attachment.sig>


More information about the Gnupg-devel mailing list