Use add_note() to annotate exceptions when encoding fails #10464
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.
We now always add variable names and contents when encoding fails, in contrast to the current practice where variable names and values are only sometimes specified, based on the
name
passed intoVariableCoder.encode()
. This provides better debugging experience for users.In the future, we might remove
name
fromVariableCoder.encode()
because this makes it redundant.For example, attempting to save a int64 fail in netCDF3 file now shows something like the following:
Note that
Exception.add_note()
is a Python 3.11+ feature, so this PR will need to wait until #10438 is submitted.whats-new.rst