From f0063afa71bc7e71f19d174acc2fde26f0c11850 Mon Sep 17 00:00:00 2001 From: Ben McGinnes Date: Tue, 15 May 2018 13:13:16 +1000 Subject: docs: python bindings HOWTO - DITA XML version * Due to the org-babel bug which breaks Python source code examples beyond the most simple snippets, ported the HOWTO to a source format which I *know* for sure won't break it. * Details of the org-mode bug is in https://dev.gnupg.org/T3977 * DITA project uses DITA-OT 2.x (2.4 or 2.5, IIRC) with support for DITA 1.3. * source files were written with oXygenXML Editor 20.0, hence the oXygenXML project file in the directory; however only the .ditamap and .dita files are required to generate any output with the DITA-OT. Signed-off-by: Ben McGinnes --- lang/python/docs/dita/howto/part02/no-pypi.dita | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 lang/python/docs/dita/howto/part02/no-pypi.dita (limited to 'lang/python/docs/dita/howto/part02/no-pypi.dita') diff --git a/lang/python/docs/dita/howto/part02/no-pypi.dita b/lang/python/docs/dita/howto/part02/no-pypi.dita new file mode 100644 index 00000000..8f2b6013 --- /dev/null +++ b/lang/python/docs/dita/howto/part02/no-pypi.dita @@ -0,0 +1,19 @@ + + + + + No PyPI + +

Most third-party Python packages and modules are available and distributed through + the Python Package Installer, known as PyPI.

+

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.

+ + + -- cgit v1.2.3