[Pkg-gnupg-commit] [gpgme] 12/412: Explaining why not all scripts work

[Daniel Kahn Gillmor]

This is an automated email from the git hooks/post-receive script.

dkg pushed a commit to branch master
in repository gpgme.

commit 29887c9b28c0db14bf75e227a8082d23a2c151d2
Author: Ben McGinnes <ben at adversary.org>
Date:   Sun May 17 05:14:47 2015 +1000

    Explaining why not all scripts work
    
    * Some of them cannot be properly tested on OS X, especially with GTK in
      the mix (it works on OS X, but is unlikely to be as easily accessible
      as Cocoa or Qt).
    * Most major functions are showcased and do work, albeit sometimes with
      false positives of error messages, at least on OS X.
---
 lang/py3-pyme/examples/Examples.rst | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/lang/py3-pyme/examples/Examples.rst b/lang/py3-pyme/examples/Examples.rst
new file mode 100644
index 0000000..18b03b2
--- /dev/null
+++ b/lang/py3-pyme/examples/Examples.rst
@@ -0,0 +1,7 @@
+===============
+Example Scripts
+===============
+
+Most of the examples have been converted to work with Python 3, just as the original versions worked with Python 2.  A small number produce errors on OS X, but may behave differently on other POSIX systems.  The GTK based scripts (PyGtkGpgKeys.py and pygpa.py) have not been modified at all.
+
+When using or referring to the example scripts here, the most common change has been the byte encoded strings, so if something does not work then chances are that it will be related to the encoding or decoding of UTF-8.

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-gnupg/gpgme.git