gpgme/lang/python
Justus Winter fe65a26ab5
python: Use one copy of the source tree per Python version.
* lang/python/Makefile.am (copystamp): Create one copy per Python
version.
(all-local): Adapt.
(clean-local): Likewise.
(install-exec-local): Likewise.
* lang/python/tests/run-tests.py: Likewise.
--

Currently, we use one copy of the Python module's source to build for
all Python versions.  This is problematic, because SWIG writes a
wrapper file into the source tree.  Currently, this file works with
both Python 2 and 3, but this is purely by chance.

Improve the situation by creating one copy per Python version so that
SWIG can write version-specific code into each copy.

Signed-off-by: Justus Winter <justus@g10code.com>
2017-02-13 16:44:53 +01:00
..
docs python: Rename Python module from PyME to gpg. 2016-10-31 15:42:27 +01:00
examples python: Use vanity modules for constants in tests and examples. 2016-10-31 15:42:35 +01:00
gpg python: Make Context have a repr method. 2016-12-01 17:37:15 +01:00
tests python: Use one copy of the source tree per Python version. 2017-02-13 16:44:53 +01:00
gpgme-h-clean.py core: Document the version a function has been deprecated. 2016-09-16 16:00:27 +02:00
gpgme.i python: default op_keylist_start parameters. 2017-01-25 17:47:35 +01:00
helpers.c python: Try to be more helpful when given a string to encrypt(). 2016-12-05 12:44:20 +01:00
helpers.h python: Rename Python module from PyME to gpg. 2016-10-31 15:42:27 +01:00
Makefile.am python: Use one copy of the source tree per Python version. 2017-02-13 16:44:53 +01:00
MANIFEST.in python: Rename Python module from PyME to gpg. 2016-10-31 15:42:27 +01:00
private.h python: Rename Python module from PyME to gpg. 2016-10-31 15:42:27 +01:00
README python: Rename Python module from PyME to gpg. 2016-10-31 15:42:27 +01:00
setup.py.in python: Require at least GPGME 1.7 for out-of-tree builds. 2016-11-09 13:57:05 +01:00

gpg - GPGME bindings for Python                                      -*- org -*-
=======================

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