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.
IOErroris raised several places indecoding.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 aValueErrorwould be more appropriate, maybe it should be a new subclass ofIOErrorto maintain compatibility with existing code that usesebmlite.There is also one
IOErrorraised in a similar situation incore.pythat should probably be some other type.