[git] GPGME - branch, ben/docs/2018-03, updated. gpgme-1.10.0-101-g431897a

[by Ben McGinnes]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GnuPG Made Easy".

The branch, ben/docs/2018-03 has been updated
       via  431897a4c48fe1bc9d37f655097aabaf5b685d11 (commit)
      from  22e2445beee46ed1e527a98e635153c7cf03786f (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 431897a4c48fe1bc9d37f655097aabaf5b685d11
Author: Ben McGinnes <ben at adversary.org>
Date:   Fri Mar 16 03:52:58 2018 +1100

    doc: python bindings howto
    
    * Added clarification on why it's not on PyPI.

diff --git a/lang/python/docs/GPGMEpythonHOWTOen.org b/lang/python/docs/GPGMEpythonHOWTOen.org
index 4aa4398..28d2e25 100644
--- a/lang/python/docs/GPGMEpythonHOWTOen.org
+++ b/lang/python/docs/GPGMEpythonHOWTOen.org
@@ -179,6 +179,14 @@
    Due to the nature of what these bindings are and how they work, it
    is infeasible to install the GPGME Python bindings in the same way.
 
+   This is because the bindings use SWIG to dynamically generate C
+   bindings against =gpgme.h= and =gpgme.h= is generated from
+   =gpgme.h.in= at compile time when GPGME is built from source.  Thus
+   to include a package in PyPI which actually built correctly would
+   require either statically built libraries for every architecture
+   bundled with it or a full implementation of C for each
+   architecture.
+
 ** Requirements
    :PROPERTIES:
    :CUSTOM_ID: gpgme-python-requirements

-----------------------------------------------------------------------

Summary of changes:
 lang/python/docs/GPGMEpythonHOWTOen.org | 8 ++++++++
 1 file changed, 8 insertions(+)


hooks/post-receive
-- 
GnuPG Made Easy
http://git.gnupg.org