f0063afa71
* 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 <ben@adversary.org>
17 lines
793 B
XML
17 lines
793 B
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE dita PUBLIC "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd">
|
|
<dita>
|
|
<topic id="topic_g4z_wxx_5db">
|
|
<title>Python Bindings</title>
|
|
<body>
|
|
<p>The Python bindings for GPGME provide a higher level means of accessing the complete
|
|
feature set of GPGME itself. It also provides a more pythonic means of calling these API
|
|
functions.</p>
|
|
<p>The bindings are generated dynamically with SWIG and the copy of <codeph>gpgme.h</codeph>
|
|
generated when GPGME is compiled.</p>
|
|
<p>This means that a version of the Python bindings is fundamentally tied to the exact same
|
|
version of GPGME used to generate that copy of <codeph>gpgme.h</codeph>.</p>
|
|
</body>
|
|
</topic>
|
|
</dita>
|