gnupg.GPG(verbose=True) passes invalid option to gpg-1.4.16 on OS X 10.9.2 about python-gnupg HOT 11 CLOSED

Just in case, if anyone had any doubt in their minds about my appreciation for GnuPG, or maybe thought I was sometimes being a little bit negative or bitchy, wondering if statements I make should be interpreted as complaints of incompetence about GnuPG's development team:

Let me make this entirely clear.

I FUCKING HATE GNUPG.

from python-gnupg.

I have the same, on a very weird Linux machine running a very weird gnupg binary… so I don't think this issue is only effecting you, @ianchesal. :)

Let me see what I can do to fix this.

from python-gnupg.

I can reproduce this using any of the following valid arguments to the verbose parameter: True, any int ≥ 1, and any of the named GnuPG logging levels, e.g. 'guru', 'basic', 'advanced', etc.

Using any of the following arguments, the bug is not triggered: 'none', None, 0, False

from python-gnupg.

Aha! Found it. The bug is that GnuPG needs to be passed the argument --debug-level=basic, not --debug-level basic. Which is also a bug in GnuPG's documentation, as the GnuPG manual states:

       --debug-level level
              Select  the debug level for investigating problems. level may be a numeric value or by a
              keyword:

Thanks for helping me find this, @ianchesal.

from python-gnupg.

Okay, this is merged into develop for 1.3.2, please let me know if this issue comes up again for you, @ianchesal, and thanks for all your help!

from python-gnupg.

There is still a problem.

I was under the impression that this issue affected all upstream branches of GnuPG (branches 1.4.x, 2.0.x, and 2.1.x) and I supplied a documentation patch, leaving the parsing behaviours intact. However, Werner Koch responded, noting that the undocumented requirement for '=' is only in GnuPG<=1.4.18, and instead patched GnuPG>=1.4.19…

Meaning that now python-gnupg needs to only add the equal sign if the GnuPG binary version is <=1.4.18.

le sigh

from python-gnupg.

Also, this is fixed again in commit b51b0eb.

from python-gnupg.

I'm going to call you up later tonight and whisper gently into your ear "You know you want to rewrite GnuPG, you know you do."

Incidentally, I only have your number because the shit PGP user experience failed you and you accidentally sent an email unencrypted.

(just kidding!)

from python-gnupg.

@isislovecruft thanks for the fix. Can't say I didn't enjoy watching you resolve this. 👍

from python-gnupg.

@petertodd I have a phone number?! That's a bug… :)

from python-gnupg.

@isis Wait, lemme guess, your not a male living in Syria are you? Because I already had to tell my other agent you're certainly not a four thousand year old religious concept.

Damn you zooko...

from python-gnupg.