GpgFrontend/gpgme
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc: python bindings howto

Browse Source 
* Added clarification on why it's not on PyPI.
This commit is contained in:
Ben McGinnes 2018-03-16 03:52:58 +11:00
parent 22e2445bee
commit 431897a4c4
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
lang/python/docs/GPGMEpythonHOWTOen.org
View File

@ -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