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

doc: python binding howto

Browse Source 
* Clarified which English dialects this is written in.
* Translating to American can happen *after* it's done.
** The Yank version would probably want to change some of the examples
   anyway.
* Began the description for normal/default signing.
This commit is contained in:
Ben McGinnes 2018-03-14 02:40:41 +11:00
parent a10dcb4f13
commit a71205dc3b
1 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -16,7 +16,8 @@
| Version: | 0.0.1-alpha | | Version: | 0.0.1-alpha |
| Author: | Ben McGinnes <ben@gnupg.org> | | Author: | Ben McGinnes <ben@gnupg.org> |
| Author GPG Key: | DB4724E6FA4286C92B4E55C4321E4E2373590E5D | | Author GPG Key: | DB4724E6FA4286C92B4E55C4321E4E2373590E5D |
| Language: | English | | Language: | Australian English, British English |
| xml:lang: | en-AU, en-GB, en |
This document provides basic instruction in how to use the GPGME This document provides basic instruction in how to use the GPGME
Python bindings to programmatically leverage the GPGME library. Python bindings to programmatically leverage the GPGME library.
@ -653,6 +654,16 @@
:CUSTOM_ID: howto-basic-signing-normal :CUSTOM_ID: howto-basic-signing-normal
:END: :END:
The normal or default signing process is essentially the same as
is most often invoked when also encrypting a message or file. So
when the encryption component is not utilised, the result is to
produce an encoded and signed output which may or may not be ASCII
armoured and which may or may not also be compressed.
By default compression will be used unless GnuPG detects that the
plaintext is already compressed. ASCII armouring will be
determined according to the value of =gpg.Context().armor=.
#+begin_src python #+begin_src python
import gpg import gpg