GpgFrontend/gpgme
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc: python bindings howto

Browse Source 
* error corrections.
* multiple typesetting fixes only required due to certain archaic
  eccentricities of LaTeX.
* a couple of minor python PEP8 compliance corrections.
This commit is contained in:
Ben McGinnes 2018-03-13 06:09:53 +11:00
parent 83b1336cee
commit a8f48b6f57
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
lang/python/docs/GPGMEpythonHOWTOen.org
View File

@ -13,9 +13,10 @@
:CUSTOM_ID: intro
:END:
Version: 0.0.1-alpha [2018-03-07 Wed]
Author: Ben McGinnes <ben@gnupg.org>
Author GPG Key: DB4724E6FA4286C92B4E55C4321E4E2373590E5D
| Version: | 0.0.1-alpha |
| Author: | Ben McGinnes <ben@gnupg.org> |
| Author GPG Key: | DB4724E6FA4286C92B4E55C4321E4E2373590E5D |
| Language: | English |
This document provides basic instruction in how to use the GPGME
Python bindings to programmatically leverage the GPGME library.
@ -349,7 +350,7 @@
Encrypting to multiple keys, in addition to a default key or a key
configured to always encrypt to, is a little different and uses a
slightly different call to the op_encrypt call demonstrated in the
slightly different call to the =op_encrypt call= demonstrated in the
previous section.
The following example encrypts a message (=text=) to everyone with
@ -360,7 +361,7 @@
#+begin_src python
import gpg
text=b"""Oh look, another test message.
text = b"""Oh look, another test message.
The same rules apply as with the previous example and more likely
than not, the message will actually be drawn from reading the
@ -640,7 +641,7 @@
* Footnotes
[fn:1] Short_History.org and/or Short_History.html.
[fn:1] =Short_History.org= and/or =Short_History.html=.
[fn:2] The =lang/python/docs/= directory in the GPGME source.