[git] GPGME - branch, master, updated. gpgme-1.12.0-23-g04791c8

by Ben McGinnes cvs at cvs.gnupg.org
Tue Oct 23 14:40:05 CEST 2018


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, master has been updated
       via  04791c896712857feaf9a472a48d7a4c4f287775 (commit)
      from  59e38e3d2c14b40045e15c45b6c2f300e8f097dc (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 04791c896712857feaf9a472a48d7a4c4f287775
Author: Ben McGinnes <ben at adversary.org>
Date:   Tue Oct 23 23:38:56 2018 +1100

    docs: python howto
    
    * Fixed a few spelling and grammatical errors.

diff --git a/lang/python/doc/src/gpgme-python-howto.org b/lang/python/doc/src/gpgme-python-howto.org
index 07026b8..3c389d1 100644
--- a/lang/python/doc/src/gpgme-python-howto.org
+++ b/lang/python/doc/src/gpgme-python-howto.org
@@ -625,10 +625,10 @@ to or which are found by GPGME's configuration stage immediately prior
 to running the make commands.  Which is exactly what the compiling and
 installing process of GPGME does by default.
 
-Once that is done, however, it appears that a copy the compiled module
-may be installed into a virtualenv of the same major and minor version
-matching the build.  Alternatively it is possible to utilise a
-=sites.pth= file in the =site-packages/= directory of a viertualenv
+Once that is done, however, it appears that a copy of the compiled
+module may be installed into a virtualenv of the same major and minor
+version matching the build.  Alternatively it is possible to utilise a
+=sites.pth= file in the =site-packages/= directory of a virtualenv
 installation, which links back to the system installations
 corresponding directory in order to import anything installed system
 wide.  This may or may not be appropriate on a case by case basis.
@@ -2876,7 +2876,7 @@ is the key IDs of the group as a string.
 The =group_lists= result is very similar in that it is a list of
 lists.  The first part, =group_lists[i][0]= matches
 =group_lines[i][0]= as the name of the group, but =group_lists[i][1]=
-is the key IDs of the group as a string.
+is the key IDs of the group as a list.
 
 A demonstration of using the =groups.py= module is also available in
 the form of the executable =mutt-groups.py= script.  This second

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

Summary of changes:
 lang/python/doc/src/gpgme-python-howto.org | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)


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




More information about the Gnupg-commits mailing list