Skip to content

Raise different exception type in decoding.py? #82

@StokesMIDE

Description

@StokesMIDE

IOError is raised several places in decoding.py; in hindsight, this is probably the wrong exception type, since it is an error in the data rather than an error accessing it. Some other exception type should be raised. While a ValueError would be more appropriate, maybe it should be a new subclass of IOError to maintain compatibility with existing code that uses ebmlite.

There is also one IOError raised in a similar situation in core.py that should probably be some other type.

Metadata

Metadata

Assignees

No one assigned

    Labels

    DecodingRelated to the importing of EBML datadevelopmentDevelopment issues: package deployment, project organization, etc.enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions