aboutsummaryrefslogtreecommitdiffstats
path: root/lang/python/docs/dita/howto/part02/installing.dita
diff options
context:
space:
mode:
authorBen McGinnes <[email protected]>2018-05-15 03:13:16 +0000
committerBen McGinnes <[email protected]>2018-05-15 03:13:16 +0000
commitf0063afa71bc7e71f19d174acc2fde26f0c11850 (patch)
treea23a33ef70f13747642a8c96e7128e41b5f7ce58 /lang/python/docs/dita/howto/part02/installing.dita
parentjson: Improve auto-base64 encoding to not split UTF-8 chars. (diff)
downloadgpgme-f0063afa71bc7e71f19d174acc2fde26f0c11850.tar.gz
gpgme-f0063afa71bc7e71f19d174acc2fde26f0c11850.zip
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 <[email protected]>
Diffstat (limited to 'lang/python/docs/dita/howto/part02/installing.dita')
-rw-r--r--lang/python/docs/dita/howto/part02/installing.dita23
1 files changed, 23 insertions, 0 deletions
diff --git a/lang/python/docs/dita/howto/part02/installing.dita b/lang/python/docs/dita/howto/part02/installing.dita
new file mode 100644
index 00000000..91a0cf49
--- /dev/null
+++ b/lang/python/docs/dita/howto/part02/installing.dita
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE dita PUBLIC "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd">
+<dita>
+ <topic id="topic_ivh_zfy_5db">
+ <title>Installing</title>
+ <body>
+ <p>Installing the Python bindings is effectively achieved by compiling and installing GPGME
+ itself.</p>
+ <p>Once SWIG is installed with Python and all the dependencies for GPGME are installed you
+ only need to confirm that the version(s) of Python you want the bindings installed for are
+ in your <codeph>$PATH</codeph>.</p>
+ <p>By default GPGME will attempt to install the bindings for the most recent or highest
+ version number of Python 2 and Python 3 it detects in <codeph>$PATH</codeph>. It
+ specifically checks for the <cmdname>python</cmdname> and <cmdname>python3</cmdname>
+ executables first and then checks for specific version numbers.</p>
+ <p>For Python 2 it checks for these executables in this order: <cmdname>python</cmdname>,
+ <cmdname>python2</cmdname> and <cmdname>python2.7</cmdname>.</p>
+ <p>For Python 3 it checks for these executables in this order: <cmdname>python3</cmdname>,
+ <cmdname>python3.6</cmdname>, <cmdname>python3.5</cmdname> and
+ <cmdname>python3.4</cmdname>.</p>
+ </body>
+ </topic>
+</dita>