Re: Future of GpgME python bindings on PyPi
Lucas Hoffmann via Gnupg-devel <[email protected]>
| Newsgroups | gmane.comp.encryption.gpg.devel |
|---|---|
| Message-ID | <174233983828.22902.2258499130036330260@yoga> |
Quoting Ingo Klöcker (2025-03-18 21:27:03) > I think now that we have finally dropped support for Python 2 the build could > be modernized. Patches are welcome. Are you talking about the pyproject.toml file that emerged in the python ecosystem? I think it is possible to move some metadata from setup.py to this file and also specify the minimum requirement for setuptools. That could free the code of the distutils references. If that is desired I can try to prepare a patch and send it to the list. > > could try to get at least the current version > > of https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgmepy.git;a=summary > > up to Pypi. It seems helpful to show that the bindings still exist. > > +1 from me. Also +1 from me. I am speaking on behalf of alot (https://github.com/pazz/alot), a mail user agent that uses the gpg python bindings. We would greatly profit from an updated PyPI package. Best Regards, Lucas _______________________________________________ Gnupg-devel mailing list [email protected] https://lists.gnupg.org/mailman/listinfo/gnupg-devel
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRZKi+BmaQnxh7D1LR4esDdEzEAtgUCZ9n+9AAKCRB4esDdEzEA thFnAP9CxV1gaxYNMv1CE8sV4T7/08etuXZ10D8wKh4cZKWGYgD/cAFUjC8T17xv JVfS0ymwUAVND78n0ZWPQ4rT96y5ugI= =+OXD -----END PGP SIGNATURE-----