| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
Python3 only supports "new-style" classes (those extending object),
and we don't need to explicitly inherit from this root class any more.
See http://pylint-messages.wikidot.com/messages:c1001
|
| |
|
|
|
|
| |
In python3 Exception doesn't have a message attribute, the only way to
get the string output is to call str() on the Exception. This also works
in python 2.7, so go ahead and make that change.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This converts from the now abandoned pygpgme project for wrapping gpgme,
to the upstream gpgme python bindings (which are descended from the pyme
project, before they became official).
Largely this change should not be user visible, but there are a couple
cases where the new bindings provide slightly more detailed error
messages, and alot directly presents those messages to users.
This patch has been significantly revised and updated by Dylan Baker,
but was originally authored by Daniel Kahn Gillmor.
Fixes #1069
|
| | |
|
| | |
|
| |
|
|
|
| |
and use them to handle AddressbookError exceptions
raised by addressbook.lookup
|
| |
|
|
|
|
|
| |
The previous statement had no effect. The super classes constructor
sets the .message attribute, so it is safe to drop that statement.
Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
|
| | |
|
| |
|
|
|
| |
to avoid import ui stuff to crypto.py I added error codes to the GPGProblem
Exceptions. This way I can process them later, depending on the error code
|
| | |
|
| |
|
|
| |
cf issue #472
|
| |
|
|
|
| |
to prevent circular imports and for consistency:
This Exception is not related to the database abstraction layer.
|
| | |
|
|
|
this refactors settings.py to make it more modular:
errors.py will contain all exception classes,
read_config is moved to helper to reuse in elsewhere
|
