<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gpgme/lang/python/setup.py.in, branch gpgme-1.23.2</title>
<subtitle>GnuPG Made Easy.</subtitle>
<id>http://git.bktus.com/gpgfrontend/gpgme/atom?h=gpgme-1.23.2</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/gpgme/atom?h=gpgme-1.23.2'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/'/>
<updated>2022-10-26T02:02:36Z</updated>
<entry>
<title>python: Fix configure generating setup.py.</title>
<updated>2022-10-26T02:02:36Z</updated>
<author>
<name>NIIBE Yutaka</name>
<email>gniibe@fsij.org</email>
</author>
<published>2022-10-26T02:02:36Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=f1802682c3c8794edaca37966405bd1f070f5e01'/>
<id>urn:sha1:f1802682c3c8794edaca37966405bd1f070f5e01</id>
<content type='text'>
* lang/python/setup.py.in: Handle the case, when substitutions
may be empty.

--

Reported-by: Andreas Metzler
Fixes-commit: ae9258fbf3b9d434495ef11fc184a91fe7c4ca57
GnuPG-bug-id: 6204
Signed-off-by: NIIBE Yutaka &lt;gniibe@fsij.org&gt;
</content>
</entry>
<entry>
<title>build:python: Don't use gpg-error-config/gpgme-config.</title>
<updated>2022-09-15T04:46:23Z</updated>
<author>
<name>NIIBE Yutaka</name>
<email>gniibe@fsij.org</email>
</author>
<published>2022-09-15T04:46:23Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=ae9258fbf3b9d434495ef11fc184a91fe7c4ca57'/>
<id>urn:sha1:ae9258fbf3b9d434495ef11fc184a91fe7c4ca57</id>
<content type='text'>
* lang/python/setup.py.in: Use @prefix@, @GPGME_CONFIG_LIBS@,
@GPGME_CONFIG_CFLAGS@, and @GPG_ERROR_CFLAGS@ of configure.

--

GnuPG-bug-id: 6204
Signed-off-by: NIIBE Yutaka &lt;gniibe@fsij.org&gt;
</content>
</entry>
<entry>
<title>python: documentation</title>
<updated>2018-11-30T20:45:50Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-11-30T20:45:50Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=3b056a01a252bb72df5744409ba494e1a6e54d31'/>
<id>urn:sha1:3b056a01a252bb72df5744409ba494e1a6e54d31</id>
<content type='text'>
* Added long description to setup.py.in.
* Added maintenance mode details with clarification for what type of
  things would be a bug as far as MM is concerned and what wouldn't
  be.
** Includes a not too subtle hint directed towards the donations page.
* Miscellaneous tightening of documentation.

Signed-off-by: Ben McGinnes &lt;ben@adversary.org&gt;
</content>
</entry>
<entry>
<title>doc: convert more http:// links to https://</title>
<updated>2018-10-18T04:28:51Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2018-10-18T04:10:19Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=a81534fed8ff34b67a2726d333d9725454663c82'/>
<id>urn:sha1:a81534fed8ff34b67a2726d333d9725454663c82</id>
<content type='text'>
--

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>Python bindings setup file</title>
<updated>2018-08-18T14:21:47Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-08-18T14:21:47Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=03b899dbe14a3c32fd018c20c7d5156366fdcc3d'/>
<id>urn:sha1:03b899dbe14a3c32fd018c20c7d5156366fdcc3d</id>
<content type='text'>
* Moved the build import back up where it belongs.
* Included comments indicating how to build and install for multiple
  Python versions beyond the first 2 on the same system.
</content>
</entry>
<entry>
<title>Python bindings setup: Near PEP8 compliance</title>
<updated>2018-08-18T08:19:16Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-08-18T08:19:16Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=fc55caccfc87253e1703df66b21917cc399fba62'/>
<id>urn:sha1:fc55caccfc87253e1703df66b21917cc399fba62</id>
<content type='text'>
* lang/python/version.py.in: Fixed most things, but there's still an
  issue near the build portion with the existing Python bugs referenced.
* lang/python/setup.py.in: Now PEP8 compliant.
</content>
</entry>
<entry>
<title>python bindings: python 3.7</title>
<updated>2018-06-29T04:26:30Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-06-29T04:26:30Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=43a2b5754571292b25402e20cd044ebda9316c77'/>
<id>urn:sha1:43a2b5754571292b25402e20cd044ebda9316c77</id>
<content type='text'>
* Bindings confirmed to work with the newly released 3.7.0.
* Updated M4 file to reflect this change and correct the Python binary
  search order (3.7 is not yet given priority, but will still be found
  first via the more generic python3 executable).
* Updated setup.py.in, bindings documentation and README to reflect this.
</content>
</entry>
<entry>
<title>python: Fix crash by leaving struct members intact</title>
<updated>2018-04-17T08:20:12Z</updated>
<author>
<name>Tobias Mueller</name>
<email>muelli@cryptobitch.de</email>
</author>
<published>2018-02-20T16:34:14Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=bbfa7c42337bb619e6af20bf051fe0755ed5a9fd'/>
<id>urn:sha1:bbfa7c42337bb619e6af20bf051fe0755ed5a9fd</id>
<content type='text'>
* lang/python/setup.py.in: Copy gpgme.h instead of parsing it.
--
The python bindings tried to parse deprecated functions
out of gpgme.h. This fails for the current gpgme.h in
that it removes an entire field in the key sig struct (_obsolete_class).
Hence, the fields were off by an int and the bindings accessed struct
members via the wrong offset. That caused python program to crash.
At least on 32bit platforms, the crash can be easily triggered by
accessing key.uids[0].signatures. On 64bit platforms the compiler
probably aligns the struct so that the missing 4 bytes are not noticed.

With this change, the python bindings will expose all functions
that gpgme exposes, including the deprecated ones.

Credits go to Justus Winter for debugging and identying the issue.

Signed-off-by: Tobias Mueller &lt;muelli@cryptobitch.de&gt;
GnuPG-bug-id: 3892
</content>
</entry>
<entry>
<title>python: Fix build in certain cases.</title>
<updated>2017-05-18T10:22:29Z</updated>
<author>
<name>Justus Winter</name>
<email>justus@g10code.com</email>
</author>
<published>2017-05-18T09:42:13Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=84a203e60b9935bd8536cd2832fbc55d7f011341'/>
<id>urn:sha1:84a203e60b9935bd8536cd2832fbc55d7f011341</id>
<content type='text'>
* lang/python/setup.py.in: Prepend the Python build dir to the list of
include directories so that it takes precedence over any other include
directory.
--
Fixes the build in case an older 'gpgme.h' is installed and is picked
up by the compiler when compiling the Python module.

Signed-off-by: Justus Winter &lt;justus@g10code.com&gt;
</content>
</entry>
<entry>
<title>python: Read gpg-error.h using the pre-processor</title>
<updated>2017-04-10T12:47:44Z</updated>
<author>
<name>Alon Bar-Lev</name>
<email>alon.barlev@gmail.com</email>
</author>
<published>2017-04-08T13:34:32Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=7309ce6f5f7c86570953a141965d4f54cd9ad9a0'/>
<id>urn:sha1:7309ce6f5f7c86570953a141965d4f54cd9ad9a0</id>
<content type='text'>
* lang/python/setup.py.in: Read gpg-error.h using the pre-processor.

--

The libgpg-error may be installed in multilib configuration in which
there is a wrapper header at /usr/include that includes the actual
header at /usr/include/*. This causes invalid errors.i generation.

Let the pre-processor extract the header content instead reading it
explicitly.

Signed-off-by: Alon Bar-Lev &lt;alon.barlev@gmail.com&gt;
</content>
</entry>
</feed>
