gpgme 2.0 ABI break (Re: Version number of GpgME python bindings on PyPi)

Hi!

On Wed, 19 Mar 2025 18:08, Andreas Metzler said:

> The original plan for splitting of C++ QT and python bindings was to
> make a quick release after the split without further changes and version

We had the very first API still in GPGME although that it has been
decreated for >20 years.  I doubt that anyone still uses it but
technically removing this API is an ABI break and as such a bump of the
major version is required.  Given hat we wanted to bump the version
anyway, it seemed to be the Right Thing to also drop that old API.

 * Removed the gpgme_attr_t enums and their functions which were
   deprecated since 2003.  [rMd54d6eaa64]

 * Removed the never implemented or announced GPGME_EXPORT_MODE_NOUID
   flags.  [rMd54d6eaa64]

 * Removed the entire trustlist feature which worked anyway only for a
   short period in 2003.  [T4834]

I planned to talk with Ingo about the release yesterday but
unfortuantely I caught a flu and won't be able to do any serious work
the next days.  But doing a release next week should be possible.


Shalom-Salam,

   Werner


p.s.
I don't really care about PyPi because I consider these platforms to be
a major security problem.  YMMV, so Bernard or whoever may take care
of PyPi stuff for gpgmepy.

-- 
The pioneers of a warless world are the youth that
refuse military service.             - A. Einstein

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

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

iIMEARYKACsWIQSHd0YfKgdOvEgNNZQZzByeCFsQegUCZ9wFnw0cd2tAZ251cGcu
b3JnAAoJEBnMHJ4IWxB6Bm4A/j8DGrfgYznqmszYxzQqqL9+EFs9wCmKuHKXiTa0
1scsAP4oh4NhC3lREQnknWlsrxa/z1QgmN3wIwfRzlJ+2cSuBQ==
=NkI8
-----END PGP SIGNATURE-----