Add support for gnupg-2.1.13's KEY_CONSIDERED status

Issue #55 closed
Florian Schmaus
created an issue

Related to #32, but I do believe it makes sense to keep track of the issues caused by gnupg API changes in separete issues. Starting with 2.1.13 gnupg introduces the KEY_CONSIDERED status, since python-gnupg is not aware of this status I get

Traceback (most recent call last):
  File "/usr/lib64/python3.3/threading.py", line 901, in _bootstrap_inner
    self.run()
  File "/usr/lib64/python3.3/threading.py", line 858, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.3/site-packages/gnupg.py", line 813, in _read_response
    result.handle_status(keyword, value)
  File "/usr/lib64/python3.3/site-packages/gnupg.py", line 308, in handle_status
    raise ValueError("Unknown status message: %r" % key)
ValueError: Unknown status message: 'KEY_CONSIDERED'

Would be great if this status could be added in python-gnupg-0.3.9

Comments (4)

  1. Log in to comment