Fix the error type for missing attributes and getattr compatibility issues #146
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The library gives incorrect behavior with
getattr:The expected result should be 2 (when the attribute does not exist, the default value 2 should be returned).
The error type for missing attributes is not consistent with Python standards:
The correct error type should be
AttributeError.These issues are all from the same root cause: when the
Dictobject is frozen and a missing attribute is accessed,AttributeErrorshould be raised (instead ofKeyError).getattrusesAttributeErrorto detect if the default value should be supplied. WhenKeyErroris raised instead,getattrwill not supply the default value.This pull request fixes these issues and adds related tests.
In more detail, the changes are:
Error for
body.missing_keyBefore:
However, the error type should be
AttributeErrorinstead. This pull request fixes this issue by catching it and throwing the correct error type:Error for
body["missing_key"]The error type for missing key access is still the same as before (KeyError) as this is the correct behavior:
getattrBefore:
The expected result should be 2. This pull request fixes the issue: