Improve error handling in _parse_scatter_color_args #17245
Merged
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.
PR Summary
Fixes #17243
The problem was that
mcolors.to_rgba_array(c)
can raise two categories of ValueErrors. One are generic array conversion-related errors, the other is our ownValueError('RGBA values should be within 0-1 range')
. Only the former should be catched and rewritten. Our ownValueError
should directly surface.I chose the simple approach of just checking the error message. One could alternatively introduce an own Exception subtype. But we're not really doing that in other places and
ValueError
seems exactly right for out-of-bounds numbers.