On 2015-10-25 at 18:21:54 +0100, Martin Manns wrote: > The reason for this breakage is a changed behavior in python-gnupg 0.3.8-1 > that > also deviates from the manual.
I've looked in the python-gnupg manual but couldn't find a description of gpg.list_keys(True).fingerprints that defines the exact content. I believe that the change is related to the fact that now python-gnupg is also considering subkey fingerprints (next-to-last item in the 0.3.8 changelog on https://bitbucket.org/vinay.sajip/python-gnupg ). I've opened a bug upstream asking for clarifications https://bitbucket.org/vinay.sajip/python-gnupg/issues/44/possible-undocumented-api-change-when -- Elena ``of Valhalla''
