python-gpg 2.0.0 from gpgmepy.git on pypi

--===============4118355256244738993==
Content-Type: multipart/signed;
  boundary="nextPart2452839.73nvsaJKx2";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2452839.73nvsaJKx2
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Python developers can now find and download
  https://pypi.org/project/gpg/2.0.0/

Thanks for Paul Schwabauer (previously Intevation) for preparations
and John Rouillard (roundup-tracker.org) for some testing.

The release is most likely suboptimal, but as the last
upload there was from 2018, I've decided to at least improve the situation
and upload what we have.

Devs can at least see that newer python bindings exist.


Werner,=20
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 mai=
n=20
branch?=20


Tech: The python module is build from libgpgme-dev on Debian GNU/Linux,
which is 1.24.2-3. But no binary wheel is shipped (this time).
Is it okay to build it from there? (I guess it is, but I am unsure.)


All: python-gpg -- the gpgme-python bindings for GnuPG - need help with=20
maintenance. (I am just the interims maintainer.) Please approach me
if you can and want to help!

Best Regards,
Bernhard


=2D-=20
https://intevation.de/~bernhard =A0 +49 541 33 508 3-3
Intevation GmbH, Osnabr=FCck, DE; Amtsgericht Osnabr=FCck, HRB 18998
Gesch=E4ftsf=FChrer: Frank Koormann, Bernhard Reiter

--nextPart2452839.73nvsaJKx2
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----

iQGzBAABCgAdFiEEvdlX+cT+D9xYPc1tK3ujv5vDpVQFAmn8pdoACgkQK3ujv5vD
pVQt9Qv/YTnlap+NUbHY2OVivKCB59WUzLJMCHeWqPjErwFDWswUShGwsPhFWyNx
cgwu23N71U3LRsvuuFGw4Ytw/bBVmb4uCiuAWYR63XxMc/kZXhNzf6UtAqNlHIz2
/tmuVCqUZVqo8XJS7ZrTPlVS4hjvMIb7NXqxwUO113BxKYV/pdZaxCkxDUQfNyR6
QUdWaHFMBaXw0tJ6cQb3hAnN+80WsvGwsVv+rxYOaUstiVZhdGZuG8AMgpyV8pj6
Snf2gM1JoOa+Zu9hQTjOwhFOwXMbRT7S6H1WgPh4bA9J0XrkBgdDqR2jSjAOqZWQ
byuGDFnjB6KZyYZGZIm2G0kws658uyVQWcZt+UgMBv5y1DdhMJIxvtISIhF7LwJp
stbV1V/pjqc4bvpQttFWsIaR4F2Y3zLB90LowuxyIteazvr4ZEF+pxJ3XmJv/zpK
FOYYrV9x2hBXXWvo7VONtkErx7oxKKd6Y+4Z7JcH6BEjGJiC2Go8FxilqG8WYAR+
L1oXmsbZ
=6Nij
-----END PGP SIGNATURE-----

--nextPart2452839.73nvsaJKx2--


--===============4118355256244738993==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gnupg-devel mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-devel

--===============4118355256244738993==--