-
Notifications
You must be signed in to change notification settings - Fork 28
Switch from subprocessing to gpg2 to PyMe #80
Comments
I just ran into a new error: This is in Debian 9 (technically in Qubes, in a Debian 9 AppVM). I made it so the GnuPG class was initialized in debug mode. Here's the output:
The signature verified successfully, and it was in fact signed with the right signing key. I think this is just an error parsing output, in my particular setup with my particular gpg2. So I think that switching from subprocessing out to gpg2 to using PyMe will solve this problem too. @samuelcouch wanna work on this issue? |
Yep – I'm working on the JSON settings rebase first, and then was going to integrate PyMe after that (or somewhat in parallel). I'll check it out then. |
https://www.gnupg.org/blog/20160921-python-bindings-for-gpgme.html this references a
Going to hold off on this until there's better support for python 3 |
If we're delaying on this, I'll remove it from the 0.1.1 milestone. |
There are major advantages to subprocessing IMO because many of the modules don't provide access to all of the routines. Including GPGME. |
GPGME is GnuPG's official API, and much more reliable than subprocessing gpg2 and trying to parse the output. We should use it instead. PyMe is the python module that interfaces with GPGME. Both are official GnuPG projects.
We should switch to those to be much more future-proof. Implementing this will also make #75 no longer a problem.
The text was updated successfully, but these errors were encountered: