gpgme python bindings release plans?

[Ben McGinnes]

On Fri, Aug 31, 2018 at 11:23:49AM +0200, Tobias Mueller wrote:
> Hi,
> 
> On Thu, 2018-08-30 at 16:44 +1000, Ben McGinnes wrote:
> > In order to dynamically generate the bindings, we
> > must have the location of gpgme.h for that specific architecture,
> > operating system and build.
> but you could still upload upload binary packages to PyPI, if you wanted
> to, no?  Because the technical reasons you cite should be covered by
> PEP513.

These bindings don't meet the requirements of PEP513.  Indeed, the
very purpose of the bindings explicitly breaks the manylinux policy
that PEP discusses.


Regards,
Ben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20180831/ec1f7752/attachment-0001.sig>