[git] GPGME - branch, ben/howto-update-03, updated. gpgme-1.10.0-185-gb97ee3e

[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/howto-update-03 has been updated
       via  b97ee3e0aacaade37371c1be58f0ce7b1d9c0732 (commit)
      from  6a527a640744990af582ffff4759591afefdbc9a (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 b97ee3e0aacaade37371c1be58f0ce7b1d9c0732
Author: Ben McGinnes <ben at adversary.org>
Date:   Fri Mar 30 14:49:26 2018 +1100

    docs: python bindings howto
    
    * Added a section on checking the version details of GPGME and the
      underlying engines.
    * This is a component of the updated workaround in the previous
      commit(s).

diff --git a/lang/python/docs/GPGMEpythonHOWTOen.org b/lang/python/docs/GPGMEpythonHOWTOen.org
index e0a2664..62d807a 100644
--- a/lang/python/docs/GPGMEpythonHOWTOen.org
+++ b/lang/python/docs/GPGMEpythonHOWTOen.org
@@ -316,6 +316,46 @@
    operation type has one.
 
 
+** GPGME and Python Bindings Versions
+   :PROPERTIES:
+   :CUSTOM_ID: howto-get-version-info
+   :END:
+
+   Essentially there are two methods for checking useful version
+   information.
+
+   The first, =gpg.core.check_version=, returns the version of GPGME
+   installed.  This should match the version of the Python bindings
+   themselves, but if the bindings have been installed separately from
+   GPGME (e.g. via PyPI, in spite of the current recommendations) then
+   a mismatch is possible and the effects may be unpredictable.
+
+   #+begin_src python
+     import gpg
+
+     print(gpg.core.check_version(version=None))
+   #+end_src
+
+   The quick way to see whether the output of =gpg.core.check_version()=
+   matches the GPGME library installed is to see if the version number
+   reported matches the first header produced by the =gpgme-tool=
+   installed with the library.
+
+   The second method, =gpg.core.get_engine_info=, returns version
+   information for the underlying engines, libraries and relevant
+   components.  It also returns the full paths of certain important
+   executables, particularly =gpg= or =gpg.exe= for the OpenPGP engine
+   and =gpgsm= or =gpgsm.exe= for the S/MIME engine.
+
+   #+begin_src python
+     import gpg
+
+     for i in range(len(gpg.core.get_engine_info())):
+	 print("{0}: version {1}".format(gpg.core.get_engine_info()[i].file_name,
+					 gpg.core.get_engine_info()[i].version))
+   #+end_src
+
+
 * Working with keys
   :PROPERTIES:
   :CUSTOM_ID: howto-keys

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

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


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