Skip to content

exception types could use a common base class #507

@foresto

Description

@foresto

The exception classes (as inherited from dbus-next) derive directly from various python exceptions, rather than sharing a single superclass.

Because of this, distinguishing dbus-related errors from other errors requires application code to wrap dbus-fast calls in their own try/except blocks, and wrap other calls in separate try/except blocks (or else catch every dbus-fast exception individually by name). The result is very cluttered code.

A coherent exception hierarchy would make dbus-fast much nicer to work with, and allow application code to be simpler and easier to read.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions