qapi/error: Repurpose QAPIError as an abstract base exception class
commit46f49468c690ff015a5b5346a279845f5e55369e
authorJohn Snow <jsnow@redhat.com>
Wed, 21 Apr 2021 19:22:26 +0000 (21 15:22 -0400)
committerMarkus Armbruster <armbru@redhat.com>
Fri, 30 Apr 2021 10:59:54 +0000 (30 12:59 +0200)
tree6f43a7ef3448b81544108649d26fbbf77c34afb7
parente81718c698a9f1a1d98edd605f508dadbffe0d4d
qapi/error: Repurpose QAPIError as an abstract base exception class

Rename QAPIError to QAPISourceError, and then create a new QAPIError
class that serves as the basis for all of our other custom exceptions,
without specifying any class properties.

This leaves QAPIError as a package-wide error class that's suitable for
any current or future errors.

(Right now, we don't have any errors that DON'T also want to specify a
Source location, but this MAY change. In these cases, a common abstract
ancestor would be desired.)

Add docstrings to explain the intended function of each error class.

Signed-off-by: John Snow <jsnow@redhat.com>
Message-Id: <20210421192233.3542904-2-jsnow@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
docs/sphinx/qapidoc.py
scripts/qapi/error.py
scripts/qapi/schema.py