[git] gnupg-doc - branch, master, updated. acf44a0babcabf2dc6aaf21d15431c022c585211

[by Justus Winter]

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 "The GnuPG website and other docs".

The branch, master has been updated
       via  acf44a0babcabf2dc6aaf21d15431c022c585211 (commit)
      from  1d36db1e021124124758952c6cf156b9dc172d46 (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 acf44a0babcabf2dc6aaf21d15431c022c585211
Author: Justus Winter <justus at g10code.com>
Date:   Fri Sep 16 11:45:51 2016 +0200

    blog: Update pyme3 blog entry.
    
    --
    Signed-off-by: Justus Winter <justus at g10code.com>

diff --git a/misc/blog.gnupg.org/drafts/20160812-python-bindings-for-gpgme.org b/misc/blog.gnupg.org/drafts/20160812-python-bindings-for-gpgme.org
index 971bbaf..88216ab 100644
--- a/misc/blog.gnupg.org/drafts/20160812-python-bindings-for-gpgme.org
+++ b/misc/blog.gnupg.org/drafts/20160812-python-bindings-for-gpgme.org
@@ -1,17 +1,16 @@
 # Python bindings for GPGME
 #+AUTHOR: Justus
-#+DATE: August 12th, 2016
+#+DATE: September 16th, 2016
 
 ** Python bindings for GPGME
 
-GPGME 1.7 includes bindings for Python >= 3.4.  The bindings are a
-port of the [[https://bitbucket.org/malb/pyme][~pyme~]] bindings to Python 3, with a small shim on top to
-provide a more idiomatic interface.  For the purposes of this post I
-will refer to the preexisting bindings that are for Python 2 only
-~pyme2~, and to our new bindings as ~pyme3~.
-
-Existing applications using ~pyme2~ should continue to work with
-little to no changes beyond what is needed to port them to Python 3.
+GPGME 1.7 includes bindings for Python >= 2.7.  The bindings are a
+port of the [[https://bitbucket.org/malb/pyme][~pyme~]] bindings to Python 3 retaining compatibility with
+Python 2.7, with a small shim on top to provide a more idiomatic
+interface.  For the purposes of this post I will refer to the
+preexisting bindings that are for Python 2 only ~pyme2~, and to our
+new bindings as ~pyme3~.  Existing applications using ~pyme2~ should
+continue to work no changes.
 
 ~pyme2~ offers an interface that is very close to that of GPGME.  This
 interface exposes all features of the underlying library, but it is
@@ -34,7 +33,7 @@ with pyme.Context(armor=True) as c:
 
 This will encrypt the given plaintext using symmetric encryption and
 the given passphrase, wrap it up using the OpenPGP protocol, and
-encode it using ascii-armor.  The plaintext is easily recovered using:
+encode it using ASCII-armor.  The plaintext is easily recovered using:
 
 #+BEGIN_SRC python
 with pyme.Context() as c:

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

Summary of changes:
 .../drafts/20160812-python-bindings-for-gpgme.org     | 19 +++++++++----------
 1 file changed, 9 insertions(+), 10 deletions(-)


hooks/post-receive
-- 
The GnuPG website and other docs
http://git.gnupg.org