Feed Advanced Search

Wed, Jan 9

aheinecke closed T3815: tests fail in 2021 as Resolved.

I sent a message to gnupg-devel about this issue as it will probably hit more people now that the keys used are expired :-(

Wed, Jan 9, 8:52 AM · qt, Python, gpgme, Bug Report
aheinecke added a commit to T3815: tests fail in 2021: rM66376f3e206a: qt: Use tofu conflict test keys without expiry.
Wed, Jan 9, 8:46 AM · qt, Python, gpgme, Bug Report
aheinecke added a comment to T3815: tests fail in 2021.

Oh,.. it is even worse. The conflict keys expired 2019-01-06 so they are actually expired right now.

Wed, Jan 9, 8:18 AM · qt, Python, gpgme, Bug Report
aheinecke claimed T3815: tests fail in 2021.
Wed, Jan 9, 8:12 AM · qt, Python, gpgme, Bug Report
werner reopened T3815: tests fail in 2021 as "Open".

I don't know why @BenM closed this bug given that he mentioned that the qt part is yet not solved.

Wed, Jan 9, 8:00 AM · qt, Python, gpgme, Bug Report

Tue, Jan 8

hedning added a comment to T3815: tests fail in 2021.

We've run into the testTofuConflict failure on NixOS. gpgme v1.12, gnupg v2.2.12.

Tue, Jan 8, 8:05 PM · qt, Python, gpgme, Bug Report

Dec 15 2018

BenM added a comment to T3505: Port GPGME's Python bindings to Windows.

Though not directly related to our issues, this bug report on the MSYS2 site reported by their users encountering trouble with GPGME provides additional weight to irreconcilable differences between MSYS2 and GnuPG:

Dec 15 2018, 8:18 PM · Feature Request, gpgme, Python

Dec 10 2018

BenM closed T3815: tests fail in 2021 as Resolved.

Though apparently resolved back in May, this is what ultimately led to T4191 and was thus only properly resolved quite recently.

Dec 10 2018, 6:19 AM · qt, Python, gpgme, Bug Report
BenM closed T4271: python gpg.Context.decrypt(verify=False) no longer works as Resolved.

Confirmed that this is indeed fixed and made the (rather minor) change to the HOWTO that was needed. No changes were needed for the example script (decrypt-file.py).

Dec 10 2018, 6:08 AM · Python, gpgme, Bug Report
BenM closed T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms as Resolved.

This has now been tested on a 32-bit Gentoo VM and it behaves as expected with 32-bit system detection and creating keys with pre-2038 expirations working.

Dec 10 2018, 4:51 AM · Python, gpgme, Bug Report

Dec 8 2018

BenM updated subscribers of T3505: Port GPGME's Python bindings to Windows.

Commit 8613727f1ee985c3cfa2c815523312914f033ffd adds considerable detail on both the issues affecting compiling and installing a Windows version of the bindings and what it would take to actually resolve it.

Dec 8 2018, 7:02 AM · Feature Request, gpgme, Python

Dec 6 2018

BenM added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

I'll deploy one on AWS somewhere briefly once I've replaced a certain external keyboard, there will almost certainly be an existing image of some Linux distro in the AWS marketplace and I'd be very surprised if it took more than an hour or two of compute time to confirm.

Dec 6 2018, 2:50 PM · Python, gpgme, Bug Report

Dec 5 2018

dkg added a comment to T4276: Context.decrypt() throws an error if *any* signature is bad.

One more semantic question about how folks think Context.decrypt(verify=True) should work: if the decrypted thing has no signature at all, should the function succeed without throwing an exception? it currently does, but the returned verify_result has its signatures member set to the empty list.

Dec 5 2018, 6:30 PM · gpgme, Python, Bug Report
BenM added a comment to T4271: python gpg.Context.decrypt(verify=False) no longer works.

Ooh, nice catch @dkg, I just stepped through each of your changes and it all looks good. I'll tweak the relevant sections of the HOWTO dealing with this in the next few days (I need to replace a keyboard here before properly diving back in) and then close this case once done.

Dec 5 2018, 4:14 PM · Python, gpgme, Bug Report
dkg added a comment to T4271: python gpg.Context.decrypt(verify=False) no longer works.

since @aheinecke merged my changes, i think this bug is now resolved. I'll let @BenM close it though :)

Dec 5 2018, 2:06 PM · Python, gpgme, Bug Report
dkg added a comment to T4276: Context.decrypt() throws an error if *any* signature is bad.

@aheinecke thanks for the merge of my other branch! sadly, that branch does *not* address this issue yet. It doesn't even test for it. :( I can work on trying to fix it (and test it) if there's a consensus that we want this particular change in behavior.

Dec 5 2018, 2:04 PM · gpgme, Python, Bug Report
aheinecke added a comment to T4276: Context.decrypt() throws an error if *any* signature is bad.

Is this fixed now?

Dec 5 2018, 11:54 AM · gpgme, Python, Bug Report
aheinecke added a commit to T4271: python gpg.Context.decrypt(verify=False) no longer works: rM65c28da4e49a: python: overhaul logic of Context.decrypt().
Dec 5 2018, 11:50 AM · Python, gpgme, Bug Report
aheinecke changed the status of T4271: python gpg.Context.decrypt(verify=False) no longer works from Open to Testing.

Ben is not even subscribed to this issue.
With the volatility of gpgme-python I think that this can easily be merged. I did a quick review and it looked good to me.

Dec 5 2018, 11:49 AM · Python, gpgme, Bug Report
werner added a comment to T4271: python gpg.Context.decrypt(verify=False) no longer works.

Needs to be merged. (Note that Phabricator does not show the branch in the tooltip for commit ids.)

Dec 5 2018, 10:44 AM · Python, gpgme, Bug Report
dkg added a comment to T4271: python gpg.Context.decrypt(verify=False) no longer works.

note that the branch also updates the test suite to make sure the verify=False case is tested.

Dec 5 2018, 6:34 AM · Python, gpgme, Bug Report
dkg created T4276: Context.decrypt() throws an error if *any* signature is bad.
Dec 5 2018, 6:18 AM · gpgme, Python, Bug Report
dkg added a commit to T4271: python gpg.Context.decrypt(verify=False) no longer works: rMac8d7238dbf1: python: overhaul logic of Context.decrypt().
Dec 5 2018, 12:51 AM · Python, gpgme, Bug Report
dkg added a comment to T4271: python gpg.Context.decrypt(verify=False) no longer works.

I've just pushed a branch dkg/fix-T4271 , currently at ac8d7238dbf165950c9844e5cb41da8eb4d37bc0 that resolves this problem.

Dec 5 2018, 12:51 AM · Python, gpgme, Bug Report

Nov 28 2018

werner triaged T4271: python gpg.Context.decrypt(verify=False) no longer works as Unbreak Now! priority.

Regression introduced with 1.12.0.

Nov 28 2018, 9:30 AM · Python, gpgme, Bug Report

Nov 27 2018

dkg added a comment to T4271: python gpg.Context.decrypt(verify=False) no longer works.

please add a unit to the test suite to make sure something like this doesn't happen in the future!

Nov 27 2018, 10:14 PM · Python, gpgme, Bug Report
dkg created T4271: python gpg.Context.decrypt(verify=False) no longer works.
Nov 27 2018, 10:10 PM · Python, gpgme, Bug Report

Nov 22 2018

dkg added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

i'd be happy to help you set up your own x86 32-bit guest VM for testing
if you like, even if you're running on x86_64 hardware. they're cheap
and easy to run, and have a delightfully small memory footprint :P just
let me know!

Nov 22 2018, 1:44 PM · Python, gpgme, Bug Report
BenM changed the status of T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms from Open to Testing.
Nov 22 2018, 10:31 AM · Python, gpgme, Bug Report

Nov 5 2018

werner closed T3354: gpgme only builds against two versions of python at once as Resolved.

I consider this bug to be solved.

Nov 5 2018, 8:44 AM · Python, gpgme, Bug Report

Nov 3 2018

BenM added a comment to T3354: gpgme only builds against two versions of python at once.

MacPorts doesn't currently ship the bindings at all, but I'll see what they need to make that a reality too.

Nov 3 2018, 12:54 PM · Python, gpgme, Bug Report
BenM added a comment to T3354: gpgme only builds against two versions of python at once.

While this is now ideal for Debian, it may cause conflicts with other downstream vendors with slightly different needs to build their packages. In particular the FreeBSD ports and/or pkg system.

Nov 3 2018, 12:43 PM · Python, gpgme, Bug Report

Oct 29 2018

werner closed T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed as Resolved.
Oct 29 2018, 9:43 AM · Python, gpgme

Oct 20 2018

BenM added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

Nesting the op_genkey() calls inside try/except statements with the exceptions being caught as "oops" and otherwise "oops" being set to None provides a means of checking whether the 2099 expiration is a problem and 2037 is not.

Oct 20 2018, 2:37 AM · Python, gpgme, Bug Report
BenM added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

Well, I guess this answers my question in T4192 regarding why op_genkey was in use.

Oct 20 2018, 1:40 AM · Python, gpgme, Bug Report
BenM added a comment to T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed.

Interesting, I'll look into it, but is there a reason for using op_genkey instead of create_key (optionally with create_subkey and/or key_add_uid)? The latter should be easier and more pythonic.

Oct 20 2018, 1:16 AM · Python, gpgme
BenM added a comment to T3354: gpgme only builds against two versions of python at once.

This should already be possible, iirc the Arch Linux maintainer patched
it in. I believe there is a 'prepare' target that takes care of all the
preparations (duh), and then you can build for every Python version by
executing the Python build system with the Python version of your choice.

Oct 20 2018, 12:53 AM · Python, gpgme, Bug Report

Oct 19 2018

dkg added a comment to T3354: gpgme only builds against two versions of python at once.

@werner, thanks for rMff6ff616aea6 -- i've backported it to debian's packaging and it lets us cleanly build against all installed versions of python.

Oct 19 2018, 11:47 PM · Python, gpgme, Bug Report

Oct 18 2018

werner added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

That is up to @BenM

Oct 18 2018, 7:56 PM · Python, gpgme, Bug Report
dkg added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

the error i'd seen earlier after reverting the change was an error due to running t-callbacks.py on its own, without the rest of the test suite framework. running it within the test suite framework (with the change reverted), it passes without a problem. I've uploaded 1.12.0-4 to debian with a patch to t-callbacks.py. I can apply it upstream, if you want me to.

Oct 18 2018, 6:20 PM · Python, gpgme, Bug Report
werner added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

See T4195 for the general problem

Oct 18 2018, 6:10 PM · Python, gpgme, Bug Report
werner assigned T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms to BenM.

I have not looked at the new error but the year 2099 is clearly a y2k38 problem. gpg has some precautions but I have not checked the key generation code. The gpgme interface uses a signed long for the expiration time, although that it parses the dates received from gpg as an unsigned long. Right now, I am not sure why we did this because an unsigned long would just work. Maybe we can change or enhance the interface. But in any case this is a general problem and not specific to this bug.

Oct 18 2018, 5:54 PM · Python, gpgme, Bug Report
werner changed the status of T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed from Open to Testing.
Oct 18 2018, 5:41 PM · Python, gpgme
werner added a commit to T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed: rMfbac11b19d97: core: Fix segv in genkey when no endtag is provided..
Oct 18 2018, 5:41 PM · Python, gpgme
werner added a comment to T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed.

@BenM thinks that swig is still the best option. Actually this case helped to find a bug in gpgme. See my next commit.

Oct 18 2018, 5:40 PM · Python, gpgme
dkg added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

The error might have to do with rM46da79e3de99a7b65748994921d6aab73b9974e7 which looks like it might run afoul of 32-bit time_t (Y2K38 problem?).

Oct 18 2018, 5:33 PM · Python, gpgme, Bug Report
dkg added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

here's me running just the specific test:

Oct 18 2018, 5:20 PM · Python, gpgme, Bug Report
dkg added a comment to T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed.

If the swig interface isn't robust, can we replace it with something that will be more robust? Or do we need to wrap it with hand-crafted error checks that describe the API's constraints? It's pretty bad form to segfault python.

Oct 18 2018, 5:01 PM · Python, gpgme
werner added a commit to T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed: rM174af15725d4: core: Return an error if NULL is provided for genkey's parms..
Oct 18 2018, 5:00 PM · Python, gpgme
dkg added a comment to T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed.

When parms is malformed but not NULL, then the error appears to be a bug in the python bindings in _wrap_gpgme_release. maybe something is going wrong because of the "cannot allocate memory" error? in particular:

Oct 18 2018, 4:52 PM · Python, gpgme
werner added a comment to T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed.

That swig based interface is not really robust and it can't be because it does not known about API requirements. I bet there are other places where mandatory parameters are not checked.

Oct 18 2018, 4:13 PM · Python, gpgme
dkg added a comment to T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed.

To deal with passing None correctly, it looks to me like the problem is inside get_parameter() in src/genkey.c -- there ought to be a check for parms being NULL, and then returning either GPG_ERR_INV_VALUE or something else. otherwise, the segfault happens inside strstr.

Oct 18 2018, 4:06 PM · Python, gpgme
dkg added a comment to T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed.

It the first error (first param = None) is a segfault in versions 1.11.1-2 (debian unstable i386) and 1.8.0-3+b2 (debian stretch amd64).

Oct 18 2018, 1:15 PM · Python, gpgme
werner changed the status of T3354: gpgme only builds against two versions of python at once from Open to Testing.
Oct 18 2018, 11:48 AM · Python, gpgme, Bug Report
werner triaged T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms as High priority.
Oct 18 2018, 11:46 AM · Python, gpgme, Bug Report
werner assigned T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed to BenM.
Oct 18 2018, 11:39 AM · Python, gpgme
werner added a comment to T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed.

Is this new in gpgme 1.12 or might it also be in older versions?

Oct 18 2018, 11:38 AM · Python, gpgme
dkg renamed T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed from python gpg segfaults when first parameter to gpg.Context().op_genkey() is None to python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed.
Oct 18 2018, 8:14 AM · Python, gpgme
dkg created T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed.
Oct 18 2018, 8:05 AM · Python, gpgme

Oct 17 2018

justus added a comment to T3354: gpgme only builds against two versions of python at once.

"dkg (Daniel Kahn Gillmor)" <noreply@dev.gnupg.org> writes:

what's the status on this? i'd love to be able to build binaries for
both python3.6 and 3.7 for debian. as it stands right now, the
python3.7 continuous integration test for debian is failing
https://ci.debian.net/data/autopkgtest/unstable/amd64/g/gpgme1.0/1158040/log.gz.

Oct 17 2018, 11:46 AM · Python, gpgme, Bug Report
werner added a commit to T3354: gpgme only builds against two versions of python at once: rMff6ff616aea6: python: Auto-check for all installed python versions..
Oct 17 2018, 10:07 AM · Python, gpgme, Bug Report
dkg added a comment to T3354: gpgme only builds against two versions of python at once.

what's the status on this? i'd love to be able to build binaries for both python3.6 and 3.7 for debian. as it stands right now, the python3.7 continuous integration test for debian is failing.

Oct 17 2018, 12:53 AM · Python, gpgme, Bug Report

Aug 9 2018

lovetox closed T3813: GPGME error: "invalid crypto engine" in the MSYS2 version as Invalid.

Ok i saw they apply custom patches to _gpgme_mkstemp which are outdated and should be revisited, sorry for the noise

Aug 9 2018, 12:11 AM · Python, gpgme, Bug Report

Aug 8 2018

lovetox reopened T3813: GPGME error: "invalid crypto engine" in the MSYS2 version as "Open".

Actually i have now more debug output and i think i found the issue

Aug 8 2018, 11:55 PM · Python, gpgme, Bug Report
lovetox closed T3813: GPGME error: "invalid crypto engine" in the MSYS2 version as Invalid.

I close this for now, this seems a problem of the mingw packages in msys2

Aug 8 2018, 11:07 PM · Python, gpgme, Bug Report

Aug 7 2018

lovetox added a comment to T3813: GPGME error: "invalid crypto engine" in the MSYS2 version.

Or with both packages installed, could i maybe debug somehow where it searches?

Aug 7 2018, 9:11 PM · Python, gpgme, Bug Report
lovetox added a comment to T3813: GPGME error: "invalid crypto engine" in the MSYS2 version.

BenM, msys2 uses pacman as packagemanager, all packages are build from source

Aug 7 2018, 8:48 PM · Python, gpgme, Bug Report
BenM added a comment to T3813: GPGME error: "invalid crypto engine" in the MSYS2 version.

Alternatively, if they wish to keep using the Python installer from python.org then they would need to drop MSys2 in favour of the same version of Microsoft Visual Studio used to compile the that specific version of Python with and use it to compile every part of the GnuPG stack, up to and including GPGME.

Aug 7 2018, 7:31 AM · Python, gpgme, Bug Report
BenM added a comment to T3813: GPGME error: "invalid crypto engine" in the MSYS2 version.

If that is indeed the case and the theory regarding runtime conflicts, currently under investigation in T3505 and T4086, also proves to be true; then MSys2 users and developers will need to cease using the precompiled versions of Python available from python.org and compile their own version of Python copy with MSys2.

Aug 7 2018, 7:17 AM · Python, gpgme, Bug Report
BenM added a comment to T3505: Port GPGME's Python bindings to Windows.

Windows 10 was obtained last week and the process of preparing a Windows build env began earlier today.

Aug 7 2018, 5:59 AM · Feature Request, gpgme, Python

Jul 25 2018

BenM added a comment to T3354: gpgme only builds against two versions of python at once.

This question and some of the answers to it on StackOverflow indicate some of the difficulties in getting SWIG generated Python modules to install at all. Essentially, though the easiest method currently available without extensive customisation of the setup.py file which would need to be done for both Python 2.7 and Python 3.x is to run /path/to/specific/pythonX.Y setup.py build and then follow that with /path/to/specific/pythonX.Y setup.py install and then follow that with renaming lang/python/build to a relevant directory and/or path name which indicates which version of python was used and the location or path it is in.

Jul 25 2018, 3:46 PM · Python, gpgme, Bug Report

Jul 23 2018

BenM added a comment to T3354: gpgme only builds against two versions of python at once.

While performing some initial investigation regarding observed discrepancies between compiling GPGME directly and the subsequent SWIG static object for T4086, confirmed the relative ease by which multiple installations would be achievable if performed as a post-build process. This would have the added advantage of being more readily customisable by package maintainers downstream and not just for Debian, it could be made to work more easily with other distributions or other posix systems too.

Jul 23 2018, 10:31 AM · Python, gpgme, Bug Report

Jul 22 2018

BenM closed T3977: GPGME Python Bindings HOWTO org-babel examples losing indenting as Resolved.

Since first observing this … annoyance … the following updates have been made: Emacs has been upgraded to version 26.1, Org-Mode has been updated multiple times, including significant changes to Babel and the XHTML export, python-mode has been updated, multiple variations on the source blocks have been attempted, the document has had any and all tabs stripped out and replaced, plus each code block has been refactored and re-entered multiple times.

Jul 22 2018, 7:18 PM · Python, gpgme

Jul 14 2018

werner added a comment to T3813: GPGME error: "invalid crypto engine" in the MSYS2 version.

if that is the case config.{guess,sub} needs to support this and we should be able to handle this the same way as other Unix platforms.

Jul 14 2018, 10:08 AM · Python, gpgme, Bug Report

Jul 13 2018

lovetox reopened T3813: GPGME error: "invalid crypto engine" in the MSYS2 version as "Open".

You seem to have reached the wrong page when searching for msys2

Jul 13 2018, 11:59 PM · Python, gpgme, Bug Report

Jul 9 2018

BenM added a comment to T3977: GPGME Python Bindings HOWTO org-babel examples losing indenting.

Even after running additional tests like converting the file to reStructuredText, fixing any remaining possible errors and then converting back, the result is that org-mode still appears to save the source correctly, but cannot export it in a correct format with babel. Certainly not to XHTML and likely not to any other format either. So that's definitely a bug.

Jul 9 2018, 3:20 PM · Python, gpgme
BenM added a comment to T3977: GPGME Python Bindings HOWTO org-babel examples losing indenting.

Massive overhaul of the entire document performed in this commit.

Jul 9 2018, 2:28 PM · Python, gpgme

Jul 6 2018

BenM added a comment to T3813: GPGME error: "invalid crypto engine" in the MSYS2 version.

Slight addendum: MSYS2 isn't even part of MinGW at all, see the commentary in this bug report. Nor is it a part of Cygwin, but apparently it is a part of a fork of Cygwin.

Jul 6 2018, 4:23 AM · Python, gpgme, Bug Report
BenM closed T3813: GPGME error: "invalid crypto engine" in the MSYS2 version as Wontfix.

Not only is this not supported, but I've now confirmed that MSYS2 isn't even supported by its own project and they direct all downloaders to their MinGW-get installer.

Jul 6 2018, 3:47 AM · Python, gpgme, Bug Report

Jul 5 2018

BenM added a comment to T3505: Port GPGME's Python bindings to Windows.

Though a CFFI/ABI solution may be the only option, it would still be preferable to get SWIG working under Windows. The reasons for this are many, but not least of which would include not needing to duplicate effort to accommodate Windows, no functionality mismatch due to using the Windows version and not needing to implement every function manually since CFFI can't generate low level bindings the same way that SWIG does.

Jul 5 2018, 8:15 AM · Feature Request, gpgme, Python

Jul 4 2018

BenM added a member for Python: BenM.
Jul 4 2018, 10:55 AM

Jun 19 2018

tookmund closed T4033: Python GPGME interact bindings as Invalid.

My bad this already exists.

Jun 19 2018, 2:45 AM · Feature Request, gpgme, Python

Jun 18 2018

tookmund created T4033: Python GPGME interact bindings in the S1 Public space.
Jun 18 2018, 8:15 PM · Feature Request, gpgme, Python
tookmund added a comment to T4001: Import and Export for python bindings.

On 06/17/2018 02:10 AM, BenM (Ben McGinnes) wrote:

The two subsequent commits are the one I mentioned above (nested try/except
statements) and followed by a major PEP8 compliance overhaul of core.py.

Thanks for the patch and welcome to the weird and wonderful world of FOSS. :)

Jun 18 2018, 7:42 PM · gpgme, patch, Python, Feature Request

Jun 17 2018

BenM closed T4001: Import and Export for python bindings as Resolved.

Patch committed to master in commit 5a80e755008bbb3f4c7f91ffccd38f26cd8b3960

Jun 17 2018, 8:10 AM · gpgme, patch, Python, Feature Request
BenM added a comment to T4001: Import and Export for python bindings.

Not to worry, we've all been pretty busy of late.

Jun 17 2018, 6:43 AM · gpgme, patch, Python, Feature Request

Jun 8 2018

tookmund added a comment to T4001: Import and Export for python bindings.

Apologies for the delay, been working on GSoC stuff.
Here's what I've got as of right now:

Jun 8 2018, 6:36 PM · gpgme, patch, Python, Feature Request

Jun 6 2018

werner triaged T4001: Import and Export for python bindings as Normal priority.
Jun 6 2018, 5:57 PM · gpgme, patch, Python, Feature Request

Jun 4 2018

BenM added a comment to T4001: Import and Export for python bindings.

Not for export, there's a few traps in there, but if you want to take a second swing at import, I'd probably accept that instead.

Jun 4 2018, 8:45 PM · gpgme, patch, Python, Feature Request

Jun 3 2018

tookmund added a comment to T4001: Import and Export for python bindings.

That makes sense. If you don't have any other patches floating around for this, would you mind if I took a crack at rewriting export?

Jun 3 2018, 12:01 AM · gpgme, patch, Python, Feature Request

Jun 2 2018

BenM added a comment to T4001: Import and Export for python bindings.

Okay, the import is pretty much a match for what I have tucked away elsewhere, to that will probably get merged as is, more or less.

Jun 2 2018, 4:00 AM · gpgme, patch, Python, Feature Request
BenM claimed T4001: Import and Export for python bindings.

Actually op_import and op_export do work, but they're the underlying SWIG bindings, not the more pythonic layer Justus added a couple of years ago. I'd been planning on fixing that this month (part of the work is in one of the ben/howto-update branches), but not merged with master until it could be documented since there's something potentially hazardous in there (exporting secret keys).

Jun 2 2018, 3:26 AM · gpgme, patch, Python, Feature Request

May 29 2018

tookmund updated the task description for T4001: Import and Export for python bindings.
May 29 2018, 9:37 PM · gpgme, patch, Python, Feature Request
tookmund updated the task description for T4001: Import and Export for python bindings.
May 29 2018, 9:36 PM · gpgme, patch, Python, Feature Request
tookmund added a project to T4001: Import and Export for python bindings: gpgme.
May 29 2018, 5:27 PM · gpgme, patch, Python, Feature Request
tookmund created T4001: Import and Export for python bindings.
May 29 2018, 5:08 PM · gpgme, patch, Python, Feature Request

May 15 2018

BenM added a comment to T3977: GPGME Python Bindings HOWTO org-babel examples losing indenting.

Webhelp version of the Python bindings HOWTO is currently available here:

May 15 2018, 7:33 AM · Python, gpgme
BenM added a comment to T3977: GPGME Python Bindings HOWTO org-babel examples losing indenting.

As a work-around for this bug I've ported the HOWTO from org-mode to DITA XML and will generate a webhelp-responsive (i.e. searchable) version to put on another website (an Amazon S3 bucket since it will be reliable and cheap) in the interim.

May 15 2018, 5:25 AM · Python, gpgme

May 14 2018

BenM changed the visibility for T3977: GPGME Python Bindings HOWTO org-babel examples losing indenting.
May 14 2018, 5:33 AM · Python, gpgme
BenM added a comment to T3977: GPGME Python Bindings HOWTO org-babel examples losing indenting.

Org-Mode was updated to today's release and further testing was conducted.

May 14 2018, 5:31 AM · Python, gpgme