GpgFrontend/gpgme
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
67ebc53b0f
gpgme/lang/python
History
Ingo Klöcker 67ebc53b0f
build,python: Support building Python bindings as nested package 
* autogen-all.sh (packages): Add lang/python.
* configure.ac: Add python to available languages if subdir exists. Add
python to nested languages if enabled to generate corresponding make
targets. Call configure script of nested python package recursively.
* lang/python/configure.ac: Check if Python bindings are built as
nested package and set GPGME_CFLAGS and GPGME_LIBS accordingly.
* lang/python/setup.py.in: Define some variables where they are used
first. Extract library directories from GPGME_LIBS variable similar
to the extraction of include directories from GPGME_CFLAGS. Adjust
library locations in case of win32 the same way as the include
locations. Prefer gpgme.h in the include directories from GPGME_CFLAGS
over the one in the prefix, so that the correct gpgme.h is taken in
case of nested builds.
--

This re-adds the ability to build the Python bindings together with
gpgme with a single `configure && make` command (if building from git).

GnuPG-bug-id: 7110
2024-06-11 14:58:00 +02:00
..
build-aux build,python: Separate Python bindings from gpgme 2024-06-11 14:57:28 +02:00
doc build,python: Build Python bindings without distutils 2024-05-29 17:04:10 +02:00
examples build,python: Build Python bindings without distutils 2024-05-29 17:04:10 +02:00
m4 build,python: Separate Python bindings from gpgme 2024-06-11 14:57:28 +02:00
src python,doc: Fix typos in documentation and source code comments 2023-10-13 09:22:36 +02:00
tests build,python: Separate Python bindings from gpgme 2024-06-11 14:57:28 +02:00
.gitignore build,python: Separate Python bindings from gpgme 2024-06-11 14:57:28 +02:00
AUTHORS build,python: Separate Python bindings from gpgme 2024-06-11 14:57:28 +02:00
autogen.rc build,python: Separate Python bindings from gpgme 2024-06-11 14:57:28 +02:00
autogen.sh build,python: Separate Python bindings from gpgme 2024-06-11 14:57:28 +02:00
ChangeLog build,python: Separate Python bindings from gpgme 2024-06-11 14:57:28 +02:00
configure.ac build,python: Support building Python bindings as nested package 2024-06-11 14:58:00 +02:00
COPYING build,python: Separate Python bindings from gpgme 2024-06-11 14:57:28 +02:00
COPYING.LESSER build,python: Separate Python bindings from gpgme 2024-06-11 14:57:28 +02:00
gpgme.i python,doc: Fix typos in documentation and source code comments 2023-10-13 09:22:36 +02:00
helpers.c python: Fix wrong use of write. 2023-05-23 15:52:25 +02:00
helpers.h python: Fix wrong use of write. 2023-05-23 15:52:25 +02:00
INSTALL build,python: Separate Python bindings from gpgme 2024-06-11 14:57:28 +02:00
Makefile.am build,python: Separate Python bindings from gpgme 2024-06-11 14:57:28 +02:00
MANIFEST.in python: makefiles 2018-10-04 21:10:46 +10:00
NEWS build,python: Separate Python bindings from gpgme 2024-06-11 14:57:28 +02:00
private.h doc: use https:// for www.gnu.org 2018-10-18 00:28:51 -04:00
README doc: convert more http:// links to https:// 2018-10-18 00:28:51 -04:00
README.org doc: convert more http:// links to https:// 2018-10-18 00:28:51 -04:00
setup.py.in build,python: Support building Python bindings as nested package 2024-06-11 14:58:00 +02:00
version.py.in python: version as integers 2018-11-22 18:00:22 +11:00

README 

                   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
                    GPG - GPGME BINDINGS FOR PYTHON
                   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━


Table of Contents
─────────────────

1 Mailing List
2 Bugs
3 Authors
4 History


The "gpg" module is a python interface to the GPGME library:
<https://www.gnupg.org/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.


1 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>


2 Bugs
══════

  Please report bugs using our bug tracker <https://bugs.gnupg.org> with
  tag (aka project) 'gpgme'.


3 Authors
═════════

  PyME was created by John Goerzen, and maintained, developed, and
  cherished by Igor Belyi, Martin Albrecht, Ben McGinnes, Justus
  Winter, 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.


4 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/>
    <https://www.complete.org/JohnGoerzen>