Right now, when an augeas function returns an error, a generic Python exception (IOError, RuntimeError, or ValueError) is raised, with no way to even known the details of the failure.
Revamp a bit the system:
create subclasses of exceptions based on the existing exception thrown, to maintain compatibility with existing users; these new exceptions have extra members 'error' (for the error code), 'msg' (for the error message), 'minor' (for the error explanations), and 'details' (for the details)
add AUG_* constants for the all the Augeas errors
simplify the own error strings to mention just the function, since the exception message will contain all the available details
turn the AUG_ENOMEM error into a Python MemoryError exception, more Pythonic
Right now, when an augeas function returns an error, a generic Python exception (
IOError
,RuntimeError
, orValueError
) is raised, with no way to even known the details of the failure.Revamp a bit the system:
AUG_*
constants for the all the Augeas errorsAUG_ENOMEM
error into a PythonMemoryError
exception, more PythonicFixes #8.