1ae3ead2cd
* The developers of Phabricator, the web front-end on dev.gnupg.org have not implemented renderers for Markdown, Org-Mode or any other common markdown like language. * They also refuse to do so. * Instead they re-invented the wheel and implemented their own version of Markdown-like thing which is incompatible with everything else. It is called Remarkup. * The developers of Phabricator and Remarkup have refused to provide conversion tools to move files to/from any format to/from Remarkup. * They expect everyone to learn their new favourite pet project. * Remarkup may or may not display Org Mode files, but if so then it is likely to only want to do so as plain text. * There is an unaffiliated and unofficial project to convert Github Markdown to Remarkup via Pandoc. This might be adapted for our use, but requires testing. * Until then exporting from Org Mode to UTF-8 text is likely the least worst plan. * Which means renaming this file to README.org first.
62 lines
2.0 KiB
Org Mode
62 lines
2.0 KiB
Org Mode
#+TITLE gpg - GPGME bindings for Python
|
|
|
|
|
|
The "gpg" module is a python interface to the GPGME library:
|
|
https://www.gnupg.org/related_software/gpgme/
|
|
|
|
"gpg" offers two interfaces, one is a high-level, curated, and
|
|
idiomatic interface that is implemented as a shim on top of the
|
|
low-level interface automatically created using SWIG.
|
|
|
|
This way we make simple things easy, while still providing the entire
|
|
functionality of the underlying library.
|
|
|
|
* Mailing List
|
|
|
|
For general discussion and help see the gnupg-users mailing list:
|
|
https://lists.gnupg.org/mailman/listinfo/gnupg-users
|
|
|
|
For development see the gnupg-devel mailing list:
|
|
https://lists.gnupg.org/mailman/listinfo/gnupg-devel
|
|
|
|
* Bugs
|
|
|
|
Please report bugs using our bug tracker using the category 'gpgme',
|
|
and topic 'python':
|
|
https://bugs.gnupg.org/gnupg/
|
|
|
|
* Authors
|
|
|
|
PyME was created by John Goerzen, and maintained, developed, and
|
|
cherished by Igor Belyi, Martin Albrecht, Ben McGinnes, and everyone
|
|
who contributed to it in any way.
|
|
|
|
In 2016 we merged a port of PyME to into the GPGME repository, and
|
|
development will continue there. Please see the VCS history for the
|
|
list of contributors, and if you do find bugs, or want to contribute,
|
|
please get in touch and help maintain the python gpg bindings.
|
|
|
|
Please see the section 'History' further down this document for
|
|
references to previous versions.
|
|
|
|
* History
|
|
|
|
- The python bindings were renamed from PyME to "gpg" in 2016.
|
|
|
|
- The bindings have been merged into the GPGME repository in 2016.
|
|
|
|
- The latest version of PyME for Python 3.2 and above (as of
|
|
May, 2015) is v0.9.1.
|
|
https://git.gnupg.org/gpgme.git/lang/py3-pyme
|
|
|
|
- The latest version of PyME for Python 2.6 and 2.7 (as of this
|
|
writing) is v0.9.0. https://bitbucket.org/malb/pyme
|
|
|
|
- A previous version of PyME v0.8.0 can be found on sourceforge:
|
|
http://pyme.sourceforge.net/
|
|
|
|
- A previous version of PyME v0.5.1 which works with GPGME v0.3.15
|
|
can be found on John Goerzen's PyME page:
|
|
http://quux.org/devel/pyme/
|
|
http://www.complete.org/JohnGoerzen
|