python: documentation fixes
* Typographic and whitespace error correction pertaining to the previous update. Signed-off-by: Ben McGinnes <ben@adversary.org>
This commit is contained in:
parent
3b056a01a2
commit
2e3a681d0c
@ -78,6 +78,9 @@ decryption, verification, validation, trust levels and so on.
|
||||
Any wanted features lacking in the Python bindings are usually lacking
|
||||
because they are missing from GPGME itself (e.g. revoking keys via the
|
||||
API) and in such cases they are usually deliberately excluded. More
|
||||
discussion of these issues can be found in the archives of the
|
||||
`gnupg-devel mailing
|
||||
list <https://lists.gnupg.org/mailman/listinfo/gnupg-devel>`__.
|
||||
|
||||
Any features existing in the dynamically generated layer for which
|
||||
people want a specific, higher level function included to make it more
|
||||
|
@ -21,7 +21,6 @@
|
||||
| Author GPG Key: | [[https://hkps.pool.sks-keyservers.net/pks/lookup?search=0xDB4724E6FA4286C92B4E55C4321E4E2373590E5D&exact=on&op=get][DB4724E6FA4286C92B4E55C4321E4E2373590E5D]] |
|
||||
| Language: | Australian English, British English |
|
||||
| Language codes: | en-AU, en-GB, en |
|
||||
#+TBLFM:
|
||||
|
||||
This document provides basic instruction in how to use the GPGME
|
||||
Python bindings to programmatically leverage the GPGME library.
|
||||
|
@ -76,7 +76,9 @@ decryption, verification, validation, trust levels and so on.
|
||||
|
||||
Any wanted features lacking in the Python bindings are usually lacking
|
||||
because they are missing from GPGME itself (e.g. revoking keys via the
|
||||
API) and in such cases they are usually deliberately excluded. More
|
||||
API) and in such cases they are usually deliberately excluded. More
|
||||
discussion of these issues can be found in the archives of the
|
||||
[[https://lists.gnupg.org/mailman/listinfo/gnupg-devel][gnupg-devel mailing list]].
|
||||
|
||||
Any features existing in the dynamically generated layer for which
|
||||
people want a specific, higher level function included to make it more
|
||||
|
@ -104,7 +104,9 @@ decryption, verification, validation, trust levels and so on.
|
||||
|
||||
Any wanted features lacking in the Python bindings are usually lacking
|
||||
because they are missing from GPGME itself (e.g. revoking keys via the
|
||||
API) and in such cases they are usually deliberately excluded. More
|
||||
API) and in such cases they are usually deliberately excluded. More
|
||||
discussion of these issues can be found in the archives of the
|
||||
@uref{https://lists.gnupg.org/mailman/listinfo/gnupg-devel, gnupg-devel mailing list}.
|
||||
|
||||
Any features existing in the dynamically generated layer for which
|
||||
people want a specific, higher level function included to make it more
|
||||
|
Loading…
Reference in New Issue
Block a user